There has been a problem with the installation recently.
See original GitHub issueBug Report
There was a problem after the recent reinstallation, and I got the following error:
[!] (plugin babel) Error: Package exports for '/Users/xxx/abc/node_modules/@babel/helper-compilation-targets' do not define a '.' subpath
src/index.js
Error: Package exports for '/Users/xxx/abc/node_modules/@babel/helper-compilation-targets' do not define a '.' subpath
Environment
- Babel version(s): v7.8.0
- Node/npm version: Node 13.0.1/npm 6.12.0
- OS: OSX 10.11.6
- Monorepo: no
- How you are using Babel: cli
Issue Analytics
- State:
- Created 4 years ago
- Reactions:10
- Comments:14 (4 by maintainers)
Top Results From Across the Web
How to troubleshoot Windows Installer errors
Identify Windows Installer issues · Click Start windows icon · Right-click Windows Installer, and then click Properties. · If the Startup type box...
Read more >If an error occurred while updating or installing macOS
The message might say that an error occurred while downloading, preparing, or installing, or that the installer is damaged or could not be ......
Read more >Installation issues - Google Workspace Admin Help
Then, try installing it again. Verify Google Update is installed correctly. You should have a non-empty folder under C:\Program Files (x86)\Google\Update\ ...
Read more >'A problem has been encountered while loading the setup ...
For me it was happening because I was trying to run the installer from the DVD ... Instead, the problem was due to...
Read more >Fixed: “There was a problem resetting your PC” error on ...
If you've recently installed a Windows update, uninstall the update to try to resolve the issue. Select the Start button, then select Settings...
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
As a workaround, you can upgrade to Node.js 13.6
In fact this is a bug in last version that i can constantly reproduce with Node 13, https://github.com/babel/babel/commit/e7961a08a839b0bfe2c5a08f2e1c7e3d436af144 so we will need a new patch version to address this