Please update babel dependencies.
See original GitHub issueWhat problem does this feature solve?
The official babel 7.0.0 has been released, but the version used by @vue/babel-preset-app is ‘beta.47’.
Thanks for your efforts to create such a great framework.
What does the proposed API look like?
Update babel dependencies’ version from ‘7.0.0-beta.47’ to ‘7.0.0’.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:16
- Comments:23 (2 by maintainers)
Top Results From Across the Web
How to upgrade to babel 7 - Stack Overflow
Use babel-upgrade. Tested on node@10.15.3, npm@6.4.1 and babel@7.4.0. You can use following script. (npx on node 5+ only) npx babel-upgrade ...
Read more >Upgrade to Babel 7
Versioning/Dependencies. Most plugins/top level packages now have a peerDependency on @babel/core . Package Renames.
Read more >@babel/eslint-parser - npm
ESLint parser that allows for linting of experimental syntax transformed by Babel. Latest version: 7.19.1, last published: 3 months ago.
Read more >Using Babel and Other Dependencies in Node.js - Medium
npm install babel-core @babel/preset-env --save-dev. Please note that we use — save-dev instead of — save . This refers to development dependencies.
Read more >Babel Version Wrong - Software - FOLIO Discussions
cat ~/.config/yarn/global/node_modules/babel-loader/package.json ... Please, upgrade your dependencies to the actual version of core-js@3.
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

@LinusBorg seems the v2.2.0 release support both babel 6 and 7 already, according to this comment https://github.com/airbnb/babel-plugin-dynamic-import-node/pull/64#issuecomment-428011905
jestneedsbabel-core@7.0.0-bridge.0to work with@babel/core@^7.0.0. I believe the reason is thatjeststill imports babel core asbabel-core, so the “bridge” is meant to force@babel/coreto be imported.