Incompatibility with Webpack (version 0.5.2)
See original GitHub issueSince the publication of version 0.5.2 the package causes error in the webpack build.
v0.5.2 introduced the usage of react-scrolllock to which webpack throws the following error:
SyntaxError: Unexpected token: name (ScrollLock) [./~/react-scrolllock/src/ScrollLock.js:10,0]
I think that might be due to the fact that react-scrolllock is using es6 syntax (classes) but is published untraspiled, but I haven’t had a chance to test that yet.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:8 (6 by maintainers)
Top Results From Across the Web
webpack - npm
Latest version: 5.75.0, last published: 2 months ago. Start using webpack in your project by running `npm i webpack`.
Read more >To v5 from v4 - webpack
Test webpack 5 compatibility ... Try to set the following options in your webpack 4 configuration and check if build still works correctly....
Read more >How I solved and debugged my Webpack issue through trial ...
When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location.
Read more >nrwl/expo incompatibility with Nodejs v18 and deprecated reps
When I try to install @nrwl/expo, I give this warnings and error. ❯ yarn add @nrwl/expo -D yarn add v1.22.10 info No lockfile...
Read more >npm installs different version than specified in package.json ...
But by doing so you have to manually check/change the version ... Since they might be incompatible with the version of react you...
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 FreeTop 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
Top GitHub Comments
@jossmac thanks for the fix 👍 Everything seems to work now
thanks @jossmac!