Faizaan
Faizaan
Was looking through the plugin. How exactly would this plugin work with assets-webpack-plugin ? The json that is emitted would contain the CDN urls for the libraries?
Hmm. So for the following webpack config, ```js { context: path.resolve(__dirname, './fixtures/app'), output: { publicPath: '', path: path.resolve(__dirname, './fixtures/output/assets-webpack-plugin') }, entry: { app: './single.js' }, plugins: [ new AssetsPlugin({ filename:...
Yes. I got that. But like I said > `assets-webpack-plugin` has no explicit effect on `dynamic-cdn-webpack-plugin`. This becomes an non-issue.
Assalamu alaikum! First off, wonderful website, masha allah :D. > but still have the text rendered as transparent in the background? ~Alternatively, a copy button could be provided next to...
I would like to work on this, if possible.
https://github.com/npm/libnpmsearch
Thinking about it, is this even an issue now? Now that Babel v7 is released (:fireworks:), just returning `^7.0.0` works, right?
@adeelibr hey :D ! this issue is already being worked on in #83. You can take a look at the other issues though.
But if you see [here](https://github.com/babel/babel-upgrade/blob/master/src/index.js#L107), they are indeed parsing the file as JSON5. Maybe some other error while reading? Was there anything printed in the console?
@jeffscottward, the current behaviour of `babel-upgrade` is to **not** write by default. Did you try with the `--write` flag?