Brad Adams

I got **this** package working fine in my webpack setup with the following: `webpack.config.js`: ``` const webpack = require('webpack') module.exports = { externals: { 'jquery': 'jQuery' }, plugins: [ new...

+1

@glennpeters haha that's the excuse we're all using 😉 On a side note, there are some great React.js tutorials out there that teach you how to get it running with...

Here's a _real-world example_ (we're using a base "building block" to construct other components via `.extend`): #### Before (using `const Component = styled.div...`)  #### After (using `const Component =...

Happy to take a look however it may be past my abilities... It seems `/src/visitors/displayNameAndId.js` is taking care of the naming @probablyup?

I've done some testing on the issue and don't appear to be getting very far, however I'll share my findings incase it can assist someone else in coming up with...

Also @probablyup I couldn't detect which version of styled-components was being used locally, it doesn't appear to be in `package.json`, _or_ my `yarn.lock` after init. Something I'm missing?

I've recently reported what appeared to be a bug to NPM and this issue was referenced, so I'll leave a bit of info here. We're running into an issue where...

Seeing the same issue using vue's `...` within a `.vue` component.

I've been getting around it _importing_ media, ie: ```jsx import audio from './song.mp3' import bgImage from './bg_image.jpg' import someLogo from './logo.png' ``` And then inserting those where necessary with js....