Parsing failed after yarn update to latest
See original GitHub issueExpected Behavior
The application should properly compile, build, and serve.
Current Behavior
Application is unable to compile (see below for logs).
Failure Information (for bugs)
The application was building properly on version 8.1.2. I required an update to latest to fix an es5/differential loading issue. I ran yarn update as per the documentation and my application no longer compiles.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
- yarn update (from version 8.1.2 -> latest)
- yarn start
Failure Logs
Receiving the following message on compilation (yarn start):
ERROR in ./index.tsx 10:16
Module parse failed: Unexpected token (10:16)
File was processed with these loaders:
* ../../../node_modules/@nrwl/web/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
| import { Provider } from 'react-redux';
| import App from './App';
> ReactDOM.render(<Provider store={store}>
| <ConnectedRouter history={history}>
| <App />
ℹ 「wdm」: Failed to compile.
No type errors found
Version: typescript 3.4.5
Other
Here are my tsconfig files (first is for global and second is for my specific application).
{
"compileOnSave": false,
"compilerOptions": {
"allowJs": true,
"sourceMap": true,
"declaration": false,
"moduleResolution": "node",
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"importHelpers": true,
"target": "es5",
"module": "esnext",
"typeRoots": ["node_modules/@types"],
"lib": ["es2017", "dom"],
"skipLibCheck": true,
"skipDefaultLibCheck": true,
"baseUrl": ".",
"rootDir": "."
},
"exclude": ["node_modules", "tmp"]
}
{
"extends": "../../tsconfig.json",
"compilerOptions": {
"jsx": "react",
"allowJs": true,
"types": ["node", "jest"]
},
"paths": {
"@components/*": ["src/components/*"],
"@environment/*": ["src/environment/*"],
"@redux/*": ["src/redux/*"]
},
"include": ["**/*.ts", "**/*.tsx"]
}
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Error Codes | Yarn - Package Manager
A file from the cache has been detected unused while installing dependencies. Running yarn cache clean will cause Yarn to remove everything inside...
Read more >yarn install failed with Module parse failed - webpack
yarn install failed with Module parse failed: Unexpected character ... I have the following configuration in my webpack.config.dev.js file
Read more >parse-server
An express module providing a Parse-compatible API server. Latest version: 5.4.0, last published: a month ago. Start using parse-server in ...
Read more >Project import errors
Failed to parse package.json or yarn.lock as valid JSON. Please check the package.json and lockfile is valid JSON, any manual manipulation of these...
Read more >(No title)
Please run: npx browserslist@latest --update-db Error [ERRPACKAGEPATHNOTEXPORTED]: Package subpath './lib/parser' is not defined by "exports" in C:\Users\ ...
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

Sorry, I meant replacing the
webpackConfigentry with@nrwl/react/plugins/babel.@sagarpatel8384 No problem! You can still use your own custom webpack if you want, just make sure to import the function from
@nrwl/react/plugins/babeland call that in your own custom config function first.