`npm start` after first `npm install` throws error[π]
See original GitHub issueπ Bug report
Description
After doing npm install for the first time, the console had 12 vulnerabilities regarding dependencies:
**Critical** Verification Bypass
Package jsonwebtoken
Dependency of express-jwt
Path express-jwt > jsonwebtoken
More info https://npmjs.com/advisories/17
**Moderate** Regular Expression Denial of Service
Package moment
Dependency of express-jwt
Path express-jwt > jsonwebtoken > moment
More info https://npmjs.com/advisories/55
**High** Forgeable Public/Private Tokens
Package jws
Dependency of express-jwt
Path express-jwt > jsonwebtoken > jws
More info https://npmjs.com/advisories/88
**Low** Regular Expression Denial of Service
Package moment
Dependency of express-jwt
Path express-jwt > jsonwebtoken > moment
More info https://npmjs.com/advisories/532
**Moderate** Out-of-bounds Read
Package base64url
Dependency of express-jwt
Path express-jwt > jsonwebtoken > jws > base64url
More info https://npmjs.com/advisories/658
**Moderate** Out-of-bounds Read
Package base64url
Dependency of express-jwt
Path express-jwt > jsonwebtoken > jws > jwa > base64url
More info https://npmjs.com/advisories/658
**Moderate** Cross-Site Scripting
Package sanitize-html
Dependency of sanitize-html
Path sanitize-html
More info https://npmjs.com/advisories/135
**Moderate** Cross-Site Scripting
Package sanitize-html
Dependency of sanitize-html
Path sanitize-html
More info https://npmjs.com/advisories/154
**Low** Prototype Pollution
Package lodash
Dependency of sanitize-html
Path sanitize-html > lodash
More info https://npmjs.com/advisories/577
**High** Prototype Pollution
Package lodash
Dependency of sanitize-html
Path sanitize-html > lodash
More info https://npmjs.com/advisories/782
**High** Prototype Pollution
Package lodash
Dependency of sanitize-html
Path sanitize-html > lodash
More info https://npmjs.com/advisories/1065
**Critical** Command Injection
Package marsdb
Patched in No patch available
Dependency of marsdb
Path marsdb
More info https://npmjs.com/advisories/1122
After these, on doing npm start
, following error occurs:
UnhandledPromiseRejectionWarning: Error: Package exports for 'F:\gsoc\OWASP\juice-shop\node_modules\hashids' do not define a './cjs' subpath
Maybe a solution to this is:
npm install sanitize-html@1.21.1
npm install express-jwt@5.3.1
Is this a regression?
Not sure.
π¬ Minimal Reproduction
- Clone the repo again in a different directory in your machine
- run
npm install
and then runnpm start
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
npm start after first npm install throws error[ π ] #1289 - GitHub
I'm guessing the hashids module changed it module structure so that the cjs import which is required for node doesn't work correctly anymore....
Read more >'npm start' returns error: "There might be a problem with the ...
In my case, I solved my problem in this way. create a .env at the root of the folder react folder; type SKIP_PREFLIGHT_CHECK=true...
Read more >npm-run-script
Description. This runs an arbitrary command from a package's "scripts" object. If no "command" is provided, it will list the available scripts.
Read more >npm start not working in vs code terminal - You.com
When all else fails, remove/reinstall node.js completely. When you get wild errors all over the board on all of your node env commands,...
Read more >sh: react-scripts: command not found after running npm start ...
The solution to the above error is to open your terminal and run the command 'npm install react-scripts' to solve the 'sh react-scripts...
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
Donβt think the other dependencies are causing problems. We actually need some of them at old and vulnerable version to showcase as they are used in challenges.
Open up an issue in the hashids repo