Version 2.1.0 not on npm
See original GitHub issueThis repo is at 2.1.0
, while the npm package (babel-plugin-transform-dynamic-import
) is at 2.0.0
. And it uses a beta version of Babel 7, while this repo is still at Babel 6.
Please update both the repo and the npm package please
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Tip: Click on a version number to view a previous ... - npm
Tip: Click on a version number to view a previous version's package page ...
Read more >Is calling "npm install" on a package of a specific (older ...
json using npm install no longer works -- there is now an incompatible dependency that I assume is somewhere in eslint's dependency tree....
Read more >npm Blog Archive: npm@2.0.0
npm @2.0.0. Last week, I released npm@2.0.0 . If you've been using npm@1.4 , it's a substantial update, but that's not why it's...
Read more >M220JS mflix-js npm install - MongoDB
npm ERR! eslint-config-react-app@"^2.1.0" from the root project ... I did not think you had node.js version older than 16 :slight_smile: ...
Read more >An Absolute Beginner Guide to Node Package Manager
package name: (myapp) version: (2.1.0) description: this is my first project entry point: ... NPM will not list them as required .
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 Free
Top 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
The package seems like someone forked it and made it work for babel 7.0.0-beta.34, https://unpkg.com/babel-plugin-transform-dynamic-import@2.0.0/
So this could just very well be a misunderstanding, since they haven’t updated the meta info in
package.json
facebook/create-react-app#4984 fixes this.