yarn start doesn't work anymore?
See original GitHub issueDoes yarn start still work for other devs? I get the following error:
C:\...\KaTeX\.yarn\$$virtual\webpack-virtual-638a34bb34\0\cache\webpack-npm-5.33.2-4831fb3d39-2132ec24db.zip\node_modules\webpack\lib\NormalModule.js:1059
return this.generator.getTypes(this);
TypeError: Cannot read property 'getTypes' of undefined
at NormalModule.getSourceTypes (C:\...\KaTeX\.yarn\$$virtual\webpack-virtual-638a34bb34\0\cache\webpack-npm-5.33.2-4831fb3d39-2132ec24db.zip\node_modules\webpack\lib\NormalModule.js:1059:25)
at _ (C:\...\KaTeX\.yarn\$$virtual\webpack-virtual-638a34bb34\0\cache\webpack-npm-5.33.2-4831fb3d39-2132ec24db.zip\node_modules\webpack\lib\stats\DefaultStatsFactoryPlugin.js:1086:36)
at C:\...\KaTeX\.yarn\$$virtual\webpack-virtual-638a34bb34\0\cache\webpack-npm-5.33.2-4831fb3d39-2132ec24db.zip\node_modules\webpack\lib\stats\DefaultStatsFactoryPlugin.js:2245:9
at Hook.eval [as call] (eval at create (C:\...\KaTeX\.yarn\cache\tapable-npm-2.2.0-516ee6aa5b-f8ed725aed.zip\node_modules\tapable\lib\HookCodeFactory.js:19:10), <anonymous>:7:16)
at C:\...\KaTeX\.yarn\$$virtual\webpack-virtual-638a34bb34\0\cache\webpack-npm-5.33.2-4831fb3d39-2132ec24db.zip\node_modules\webpack\lib\stats\StatsFactory.js:277:7
at StatsFactory._forEachLevel (C:\...\KaTeX\.yarn\$$virtual\webpack-virtual-638a34bb34\0\cache\webpack-npm-5.33.2-4831fb3d39-2132ec24db.zip\node_modules\webpack\lib\stats\StatsFactory.js:100:19)
at StatsFactory._create (C:\...\KaTeX\.yarn\$$virtual\webpack-virtual-638a34bb34\0\cache\webpack-npm-5.33.2-4831fb3d39-2132ec24db.zip\node_modules\webpack\lib\stats\StatsFactory.js:276:9)
at StatsFactory.create (C:\...\KaTeX\.yarn\$$virtual\webpack-virtual-638a34bb34\0\cache\webpack-npm-5.33.2-4831fb3d39-2132ec24db.zip\node_modules\webpack\lib\stats\StatsFactory.js:137:16)
at C:\...\KaTeX\.yarn\$$virtual\webpack-virtual-638a34bb34\0\cache\webpack-npm-5.33.2-4831fb3d39-2132ec24db.zip\node_modules\webpack\lib\stats\StatsFactory.js:215:24
at Array.map (<anonymous>)
Out of habit, I tried npm install and npm start and this actually worked fine. So perhaps I’m just using Yarn incorrectly? yarn --version reports 2.2.0. (I do wonder whether it’s still worth sticking with Yarn, given the many improvements to NPM in recent years.)
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Error: yarn start - error Command "start" not found
I was trying to run a command that it is not in my scripts. Specifically, yarn start is not in the scripts part...
Read more >Yarn Start not working : r/react - Reddit
First, it sounds like you have not defined a start script in your package.json. You should add the "start" script in the "scripts"...
Read more >`yarn start` fails with error message · Issue #1155 - GitHub
The underlying issue was that the yarn path was set incorrectly. If you have this error then you will see a yarn-error.log file...
Read more >Troubleshooting | Yarn
If you get it, it very likely means that your application is not running with the PnP resolver, meaning that your require calls...
Read more >Fix Unable to Run Yarn in Windows Terminal - PowerShell
If you run into an error with your brand new machine when trying to run any custom scripts like npm, yarn or any...
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

I could reproduce the issue on my Windows machine, however I cannot pinpoint the source of the issue. It seems like webpack or webpack-dev-server issue and I’ve opened https://github.com/webpack/webpack-dev-server/issues/3235.
As reported in https://github.com/webpack/webpack-dev-server/issues/3235, this was fixed in a recent update to webpack. I confirmed that I no longer have issues with KaTeX’s master branch.