You may need an appropriate loader to handle this file type.
See original GitHub issueI have recently upgraded my React app with yarn upgrade
and that broke my app with the following error.
./node_modules/@material-ui/core/TableSortLabel/TableSortLabel.js
Module parse failed: Unexpected token (72:21)
You may need an appropriate loader to handle this file type.
|
| /* Styles applied to the icon component if `direction="desc"`. */
| iconDirectionDesc
- This is not a v0.x issue.
- I have searched the issues of this repository and believe that this is not a duplicate.
Your Environment 🌎
Tech | Version |
---|---|
Material-UI | v3.9.0 |
React | 16.7.0 |
Browser | Chrome |
Babel | 6.26.0 |
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:8 (6 by maintainers)
Top Results From Across the Web
"You may need an appropriate loader to handle this file ...
js file is doing is importing react, but it seems like the 'babel-loader' is not working. I am using 'babel-loader' 6.0.0. javascript ·...
Read more >You may need an appropriate loader to handle this file type
The “You may need an appropriate loader to handle this file type” error is encountered in the command prompt of Windows or Linux...
Read more >Module parse failed: Unexpected token. You may need an ...
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. #996.
Read more >You may need an appropriate loader to handle this file type ...
I 'm having a problem configuring Webpack for Typescript and React. After running the NPM script: webpack serves ./webpack/webpack.config.ts ...
Read more >You might need an appropriate loader to handle the file ...
You may need an appropriate loader to handle this file type. | var tokenString = localStorage.getItem("token");. | var userToken = JSON.parse( ...
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
That’s actually perfect in this case. Oftentimes a snippet is enough to gauge where the issue is with a short snippet but for build related things a full repro is the gold standard.
I have tried yarn v1.10.1 and npm v5.6.0. No issue.