I have a node.js application that I want to run on an Ubuntu 20.4 server, when I try to run the command npm install, I see the following error, I do not have root access on the server, where can this problem be? I have version 6.14.3 of npm and version 14.15.3, how can i deal with this problem?
```
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion#1, but package-lock.json was generated for lockfileVersion#2. I'll try to do my best with it!
> core-js#2.6.12 postinstall /var/www/site/public_html/node_modules/#nuxt/babel-preset-app/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
> core-js#3.10.2 postinstall /var/www/site/public_html/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
> bootstrap-vue#2.21.2 postinstall /var/www/site/public_html/node_modules/bootstrap-vue
> opencollective || exit 0
sh: 1: opencollective: Permission denied
> nuxt#2.15.4 postinstall /var/www/site/public_html/node_modules/nuxt
> opencollective || exit 0
sh: 1: opencollective: Permission denied
> swiper#5.4.5 postinstall /var/www/site/public_html/node_modules/swiper
> echo "Love Swiper? Support Vladimir's work by donating or pledging on patreon:
> https://patreon.com/vladimirkharlampidi
"
Love Swiper? Support Vladimir's work by donating or pledging on patreon:
> https://patreon.com/vladimirkharlampidi
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.3.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 1334 packages from 697 contributors and audited 1338 packages in 17.59s
102 packages are looking for funding
run `npm fund` for details
found 58 vulnerabilities (39 moderate, 18 high, 1 critical)
run `npm audit fix` to fix them, or `npm audit` for details
```
This might have the issue with permission
Try this
sudo npm cache clean
sudo npm install
Related
I have a nodejs project docker build that was building just fine on Azure Pipeline. But about 10 days ago, the build output changed to have one additional line that I do not understand the cause of it. Its the line "+ xlsx#0.17.0" at the bottom (in bold in output below).
Nothing has changed in the code between when the output didn't have that additional line and now.
Nothing was changed in the docker file or build definition as well. In the package.json, I am referencing "xlsx: ^0.14.5". Even if I change that to just "xlsx: 0.14.5" the output log will contain "+ xlsx#0.17.0" which confuses me. Shouldn't it try to install exactly that version?
NOTE: The reason I ask is because when this docker image gets pushed to Amazon ECS, it throws "Module not found 'xlsx'" Error.
THank you for your help!
found 10 vulnerabilities (2 low, 4 moderate, 4 high)
run `npm audit fix` to fix them, or `npm audit` for details
> nodemon#1.19.4 postinstall /srv/node_modules/nodemon
> node bin/postinstall || exit 0
Love nodemon? You can now support the project via the open collective:
> https://opencollective.com/nodemon/donate
npm WARN pg-cursor#2.7.1 requires a peer of pg#^8 but none is installed. You must install peer dependencies yourself.
npm WARN swagger-ui-express#4.1.6 requires a peer of express#>=4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.3.2 (node_modules/jest-haste-map/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
***+ xlsx#0.17.0***
added 663 packages from 361 contributors and updated 2 packages in 11.462s
39 packages are looking for funding
run `npm fund` for details
fixed 1 of 10 vulnerabilities in 1394 scanned packages
4 vulnerabilities required manual review and could not be updated
4 package updates for 5 vulnerabilities involved breaking changes
(use `npm audit fix --force` to install breaking changes; or refer to `npm audit` for steps to fix these manually)
Removing intermediate container 4c02dbafa75c
---> c010404a92cb
Step 9/30 : ADD . .
---> d1925852f28b
I can't comment so I will ask here:
Are you adding the package-lock.json file to the docker image? You're probably not, that's why npm is installing a newer version of the package.
That may fix the error if it's currently working on your dev environment. If not, how are you importing the package?
loadDep:fsevents -> reque - |##########---------------------------------------|
WARN engine fsevents#2.3.2: wanted: {"node":"^8.16.0 || ^10.6.0 || >=11.0.0"} (c/home/gapvak-cs3/.npm-global/bin/nodemon -> /home/gapvak-cs3/.npm-global/lib/node_modules/nodemon/bin/nodemon.js
> nodemon#2.0.12 postinstall /home/gapvak-cs3/.npm-global/lib/node_modules/nodemon
> node bin/postinstall || exit 0
Love nodemon? You can now support the project via the open collective:
> https://opencollective.com/nodemon/donate
/home/gapvak-cs3/.npm-global/lib
`-- nodemon#2.0.12
npm WARN optional Skipping failed optional dependency /nodemon/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents#2.3.2
it is just a warning on OSx, you can force installation with
npm install -f
after i use npm install sass in cmd
then cmd show these errors
npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\me\package.json'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.3.1 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\me\package.json'
npm WARN me No description
npm WARN me No repository field.
npm WARN me No README data
npm WARN me No license field.
+ sass#1.32.8
added 15 packages from 18 contributors and audited 16 packages in 3.402s
1 package is looking for funding
run `npm fund` for details
found 0 vulnerabilities
i dont know how to solve these errors
Those are just npm warnings about the package you are installing, in your case you don't have to worry about them unless something is not working. You can ignore them if you like by running:
npm install sass --silent
npm docs
After struggling for days, searching StackOverflow, and reading tutorials, I am stuck with react installation. I am sharing step by step of what I did.
Node version is 14.15.3.
Run npx create-react-app blog and this is the result:
`Creating a new React app in C:\My Garbage\Html & CSS\React.js\blog.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
> core-js#2.6.12 postinstall C:\My Garbage\Html & CSS\React.js\blog\node_modules\babel-runtime\node_modules\core-js
> node -e "try{require('./postinstall')}catch(e){}"
> core-js#3.8.1 postinstall C:\My Garbage\Html & CSS\React.js\blog\node_modules\core-js
> node -e "try{require('./postinstall')}catch(e){}"
> core-js-pure#3.8.1 postinstall C:\My Garbage\Html & CSS\React.js\blog\node_modules\core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"
> ejs#2.7.4 postinstall C:\My Garbage\Html & CSS\React.js\blog\node_modules\ejs
> node ./postinstall.js
+ react#17.0.1
+ react-scripts#4.0.1
+ cra-template#1.1.1
+ react-dom#17.0.1
added 1903 packages from 721 contributors and audited 1907 packages in 116.704s
124 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Initialized a git repository.
Installing template dependencies using npm...
npm WARN tsutils#3.17.1 requires a peer of typescript#>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.1.3 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.2.1 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.2.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules\watchpack-chokidar2\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules\webpack-dev-server\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
+ #testing-library/jest-dom#5.11.6
+ web-vitals#0.2.4
+ #testing-library/user-event#12.6.0
+ #testing-library/react#11.2.2
added 29 packages from 77 contributors and audited 1936 packages in 10.711s
124 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Removing template package using npm...
npm WARN tsutils#3.17.1 requires a peer of typescript#>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.2.1 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.2.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules\watchpack-chokidar2\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.1.3 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules\webpack-dev-server\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
removed 1 package and audited 1935 packages in 6.56s
124 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Created git commit.
Success! Created blog at C:\My Garbage\Html & CSS\React.js\blog
Inside that directory, you can run several commands:
npm start
Starts the development server.
npm run build
Bundles the app into static files for production.
npm test
Starts the test runner.
npm run eject
Removes this tool and copies build dependencies, configuration files
and scripts into the app directory. If you do this, you can’t go back!
We suggest that you begin by typing:
cd blog
npm start
Happy hacking!`
cd blog
Now while running npm start i am getting this error:
$ npm start
> blog#0.1.0 start C:\My Garbage\Html & CSS\React.js\blog
> react-scripts start
'CSS\React.js\blog\node_modules\.bin\' is not recognized as an internal or external command,
operable program or batch file.
internal/modules/cjs/loader.js:883
throw err;
^
Error: Cannot find module 'C:\My Garbage\react-scripts\bin\react-scripts.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
at Function.Module._load (internal/modules/cjs/loader.js:725:27)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! blog#0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the blog#0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\JYOTIRMOY\AppData\Roaming\npm-cache\_logs\2020-12-29T10_59_15_177Z-debug.log```
Hoping for your valuable help :)
I'd advise you to use more 'normal' paths for your projects.
Computers dislike spaces, but have learned to deal with them.
But the & sign in your path breaks the command. Bash interprets it as
blog#0.1.0 start C:\My Garbage\Html & CSS\React.js\blog, which is why it tells you that it couldn't find 'CSS\React.js\blog\node_modules...'
The easiest way to fix it is renaming your folder to something without &
Strange one today, wondering if you can help.
I recently reformatted my work laptop, and reinstalled all my tooling. Strangely, I'm finding I have to run npm install in full, before I can run yarn and yarn sb (which simply performs our storybook/start process) on new git cloned projects.
Simply running yarn as you can observe below, results in an error regarding Error: Cannot find module './es6.array.iterator'.
Any ideas why this may be? It appears npm install is doing some extra compilation steps yarn is not, I was of the understanding yarn would do everything npm install would do but a little more efficiently.
/* TRIED YARN BY ITSELF - FAILED */
PS C:\dev\projects\react-components-ts> yarn
yarn install v1.22.4
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info fsevents#1.2.13: The platform "win32" is incompatible with this module.
info "fsevents#1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents#2.1.3: The platform "win32" is incompatible with this module.
info "fsevents#2.1.3" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning " > material-table#1.66.0" has unmet peer dependency "#date-io/core#^1.3.6".
warning "material-table > #material-ui/pickers#3.2.10" has unmet peer dependency "#date-io/core#^1.3.6".
warning "#storybook/addon-actions > #storybook/api#5.3.19" has unmet peer dependency "regenerator-runtime#*".
warning "#storybook/addon-docs > #egoist/vue-to-react#1.1.0" has unmet peer dependency "vue#^2.6.10".
warning "#storybook/addon-docs > vue-docgen-loader#1.5.0" has unmet peer dependency "webpack#>=4".
warning " > #storybook/addon-storysource#5.3.19" has unmet peer dependency "#storybook/source-loader#*".
warning " > babel-loader#8.1.0" has unmet peer dependency "webpack#>=2".
[5/5] Building fresh packages...
$ tsdx build
Error: Cannot find module './es6.array.iterator'
Require stack:
- C:\dev\projects\react-components-ts\node_modules\babel-runtime\node_modules\core-js\library\modules\web.dom.iterable.js
- C:\dev\projects\react-components-ts\node_modules\babel-runtime\node_modules\core-js\library\fn\get-iterator.js
- C:\dev\projects\react-components-ts\node_modules\babel-traverse\lib\index.js
- C:\dev\projects\react-components-ts\node_modules\tsdx\dist\errors\extractErrors.js
- C:\dev\projects\react-components-ts\node_modules\tsdx\dist\createRollupConfig.js
- C:\dev\projects\react-components-ts\node_modules\tsdx\dist\createBuildConfigs.js
- C:\dev\projects\react-components-ts\node_modules\tsdx\dist\index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:957:15)
at Function.Module._load (internal/modules/cjs/loader.js:840:27)
at Module.require (internal/modules/cjs/loader.js:1019:19)
at require (internal/modules/cjs/helpers.js:77:18)
at Object.<anonymous> (C:\dev\projects\react-components-ts\node_modules\babel-runtime\node_modules\core-js\library\modules\web.dom.iterable.js:1:1)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
at Module.load (internal/modules/cjs/loader.js:977:32)
at Function.Module._load (internal/modules/cjs/loader.js:877:14)
at Module.require (internal/modules/cjs/loader.js:1019:19)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
/* BUILT EXTRA STUFF */
PS C:\dev\projects\react-components-ts> npm i
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
npm WARN deprecated os-homedir#2.0.0: This is not needed anymore. Use `require('os').homedir()` instead.
npm WARN deprecated left-pad#1.3.0: use String.prototype.padStart()
npm WARN deprecated popper.js#1.16.1: You can find the new Popper v2 at #popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated core-js#1.2.7: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated chokidar#2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated rollup-plugin-babel#4.4.0: This package has been deprecated and is no longer maintained. Please use #rollup/plugin-babel.
npm WARN deprecated core-js#2.6.11: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated request-promise-native#1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
> husky#4.2.5 preuninstall C:\dev\projects\react-components-ts\node_modules\husky
> node husky uninstall
husky > Uninstalling git hooks
husky > Done
npm WARN rm not removing C:\dev\projects\react-components-ts\node_modules\.bin\jest.cmd as it wasn't installed by C:\dev\projects\react-components-ts\node_modules\jest
npm WARN rm not removing C:\dev\projects\react-components-ts\node_modules\.bin\jest as it wasn't installed by C:\dev\projects\react-components-ts\node_modules\jest
npm WARN rm not removing C:\dev\projects\react-components-ts\node_modules\.bin\rimraf.cmd as it wasn't installed by C:\dev\projects\react-components-ts\node_modules\rimraf
npm WARN rm not removing C:\dev\projects\react-components-ts\node_modules\.bin\rimraf as it wasn't installed by C:\dev\projects\react-components-ts\node_modules\rimraf
npm WARN rm not removing C:\dev\projects\react-components-ts\node_modules\.bin\semver.cmd as it wasn't installed by C:\dev\projects\react-components-ts\node_modules\semver
npm WARN rm not removing C:\dev\projects\react-components-ts\node_modules\.bin\semver as it wasn't installed by C:\dev\projects\react-components-ts\node_modules\semver
npm WARN rm not removing C:\dev\projects\react-components-ts\node_modules\.bin\detect.cmd as it wasn't installed by C:\dev\projects\react-components-ts\node_modules\detect-port
npm WARN rm not removing C:\dev\projects\react-components-ts\node_modules\.bin\detect-port.cmd as it wasn't installed by C:\dev\projects\react-components-ts\node_modules\detect-port
npm WARN rm not removing C:\dev\projects\react-components-ts\node_modules\.bin\detect as it wasn't installed by C:\dev\projects\react-components-ts\node_modules\detect-port
npm WARN rm not removing C:\dev\projects\react-components-ts\node_modules\.bin\detect-port as it wasn't installed by C:\dev\projects\react-components-ts\node_modules\detect-port
> husky#4.2.5 install C:\dev\projects\react-components-ts\node_modules\husky
> node husky install
husky > Setting up git hooks
husky > Done
> core-js#2.6.11 postinstall C:\dev\projects\react-components-ts\node_modules\#babel\polyfill\node_modules\core-js
> node -e "try{require('./postinstall')}catch(e){}"
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
> core-js#2.6.11 postinstall C:\dev\projects\react-components-ts\node_modules\babel-runtime\node_modules\core-js
> node -e "try{require('./postinstall')}catch(e){}"
> core-js#3.6.5 postinstall C:\dev\projects\react-components-ts\node_modules\core-js
> node -e "try{require('./postinstall')}catch(e){}"
> core-js-pure#3.6.5 postinstall C:\dev\projects\react-components-ts\node_modules\core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"
> ejs#2.7.4 postinstall C:\dev\projects\react-components-ts\node_modules\ejs
> node ./postinstall.js
Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)
> husky#4.2.5 postinstall C:\dev\projects\react-components-ts\node_modules\husky
> opencollective-postinstall || exit 0
Thank you for using husky!
If you rely on this package, please consider supporting our open collective:
> https://opencollective.com/husky/donate
> jsonpath#1.0.2 postinstall C:\dev\projects\react-components-ts\node_modules\jsonpath
> node lib/aesprim.js > generated/aesprim-browser.js
> #dhi/react-components-ts#0.2.6 prepare C:\dev\projects\react-components-ts
> tsdx build
✓ Creating entry file 18.7 secs
✓ Building modules 1.1 mins
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules\jest-haste-map\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN notsup Unsupported engine for watchpack-chokidar2#2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"12.16.3","npm":"6.14.4"})
npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2#2.0.0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.1.2 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN acorn-dynamic-import#4.0.0 requires a peer of acorn#^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #egoist/vue-to-react#1.1.0 requires a peer of vue#^2.6.10 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-config-react-app#5.2.1 requires a peer of #typescript-eslint/eslint-plugin#2.x but none is installed. You must install peer dependencies yourself.
npm WARN eslint-config-react-app#5.2.1 requires a peer of #typescript-eslint/parser#2.x but none is installed. You must install peer dependencies yourself.
npm WARN eslint-config-react-app#5.2.1 requires a peer of eslint#6.x but none is installed. You must install peer dependencies yourself.
npm WARN eslint-plugin-react-hooks#2.5.1 requires a peer of eslint#^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #dhi/react-components-ts#0.2.6 No repository field.
added 291 packages from 79 contributors, removed 188 packages, updated 2114 packages and audited 2414 packages in 334.47s
162 packages are looking for funding
run `npm fund` for details
found 2 vulnerabilities (1 low, 1 moderate)
run `npm audit fix` to fix them, or `npm audit` for details
/* NOW YARN RUNS FINE - WITH OBVIOUS package-lock WARNING */
PS C:\dev\projects\react-components-ts> yarn
yarn install v1.22.4
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
$ tsdx build
✓ Creating entry file 7.3 secs
✓ Building modules 12.2 secs
Done in 21.32s.
/* AND WE CAN RUN OUR PROJECT */
PS C:\dev\projects\react-components-ts> yarn sb
yarn run v1.22.4
$ start-storybook -p 6006
info #storybook/react v5.3.19
info
info => Loading presets
info => Loading presets
info => Loading config/preview file in "./.storybook".
info => Adding stories defined in ".storybook\main.js".
info => Using default Webpack setup.
info => Using base config because react-scripts is not installed.
webpack built 19b2af886909fb20a73e in 53119ms
╭────────────────────────────────────────────────────╮
│ │
│ Storybook 5.3.19 started │
│ 26 s for manager and 55 s for preview │
│ │
│ Local: http://localhost:6006/ │
│ On your network: http://172.16.125.17:6006/ │
│ │
╰────────────────────────────────────────────────────╯
No issues found.
try to do:
yarn config set ignore-engines true
and then
yarn