ReferenceError: Unknown plugin "remove-comments"
See original GitHub issueHi 😀,
First of all - thank you for maintaining this repo.
I’m trying to update iterall
to v1.2.1
in a react-native
app (version 0.44.3
) but my packager displays the following error :
ReferenceError: Unknown plugin "remove-comments" specified in "myApp/node_modules/iterall/package.json" at 0, attempted to resolve relative to "myApp/node_modules/iterall"
Maybe it would be better to separate the babel configuration in a .babelrc
file and ignore this .babelrc
file in .npmignore
file ?
Greetings from Paris
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:9 (4 by maintainers)
Top Results From Across the Web
iterall devDependencies · Issue #656 · ardatan/graphql-tools · GitHub
I now have to add remove-comments plugin to my p... ... Module build failed: ReferenceError: Unknown plugin "remove-comments" specified in ...
Read more >Building for production causes errors in module package.json
... Module build failed: ReferenceError: Unknown plugin ... 'app/index.html', minify: { removeComments: true, collapseWhitespace: true, ...
Read more >TerserWebpackPlugin | webpack
This plugin uses terser to minify/minimize your JavaScript. Getting Started. Webpack v5 comes with the latest terser-webpack-plugin out of the box. If you...
Read more >inversify/InversifyJS - Gitter
I'm trying to write a server application which loads plugins (as you can see here). These plugins are transpiled seperatly. Inversify is throwing...
Read more >TSConfig Option: removeComments - TypeScript
TSConfig. removeComments. Customize. Site Colours: System, Always Light, Always Dark. Code Font: Cascadia, Cascadia (ligatures), Consolas, Dank Mono ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just released v1.2.2 that includes the fix for this issue
Anyway, I can confirm that by removing babel config from
package.json
it works just fine, so it’s the only issue it seems.