I tried to install Firebase all this morning. I follow the tutorial officially on setup Firebase hosting with the command line:
npm install -g firebase-tools
But it keep having trouble with error, here's the error message
pm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN deprecated har-validator#5.1.3: this library is no longer supported
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
changed 647 packages, and audited 648 packages in 10s
38 packages are looking for funding
run `npm fund` for details
11 vulnerabilities (8 moderate, 3 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
pshyduc#pshyducs-Air ~ % npm audit
found 0 vulnerabilities
pshyduc#pshyducs-Air ~ % npm audit fix
up to date, audited 1 package in 60ms
found 0 vulnerabilities
pshyduc#pshyducs-Air ~ %
I already search and following steps on npm support
But on step 5 it said, do note that I don't know how to create or modify profile on VSCode so I go straight for NPM_CONFIG_PREFIX=~/.npm-global
pshyduc#pshyducs-Air ~ % source ~/.profile
source: no such file or directory: /Users/pshyduc/.profile
Appreciate all the help
After finding along, I finally found a solution, it's hidden in the Firebase Documentation.
Not very user friendly
Just use this command and you'll be all good
curl -sL https://firebase.tools | bash
Related
I am trying to make a website using react on Mac, however, I keep getting these npm warn errors. It says there are 6 high severity vulnerabilities. How do I fix these error so that I can make the react app without any issues?
I tried uninstalling node.js and re-installing it, but it didn't seem to fix anything. Here are the errors I am getting in the terminal:
npm WARN deprecated stable#0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated rollup-plugin-terser#7.0.2: This package has been deprecated and is no longer maintained. Please use #rollup/plugin-terser
npm WARN deprecated w3c-hr-time#1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated sourcemap-codec#1.4.8: Please use #jridgewell/sourcemap-codec instead
npm WARN deprecated svgo#1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
added 1416 packages, and audited 1417 packages in 45s
231 packages are looking for funding
run `npm fund` for details
6 high severity vulnerabilities
To address all issues, run:
npm audit fix
Run `npm audit` for details.
A template was not provided. This is likely because you're using an outdated version of create-react-app.
Please note that global installs of create-react-app are no longer supported.
You can fix this by running npm uninstall -g create-react-app or yarn global remove create-react-app before using create-react-app again
I installed expo-cli in ubuntu using npm install --global expo-cli and it installed with some warning.
npm WARN deprecated source-map-url#0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated stable#0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
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 source-map-resolve#0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated subscriptions-transport-ws#0.9.8: The `subscriptions-transport-ws` package is no longer maintained. We recommend you use `graphql-ws` instead. For help migrating Apollo software to `graphql-ws`, see https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscriptions-transport-ws For general help using `graphql-ws`, see https://github.com/enisdenjo/graphql-ws/blob/master/README.md
npm WARN deprecated svgo#1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated graphql-tools#3.0.0: This package has been deprecated and now it only exports makeExecutableSchema.\nAnd it will no longer receive updates.\nWe recommend you to migrate to scoped packages such as #graphql-tools/schema, #graphql-tools/utils and etc.\nCheck out https://www.graphql-tools.com to learn what package you should use instead
added 1474 packages, and audited 1475 packages in 15s
121 packages are looking for funding
run `npm fund` for details
26 vulnerabilities (6 moderate, 17 high, 3 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
Then I tried to create a new project using expo init newapp with blank template. But it failed and showing an error log given below
✔ Choose a template: › blank a minimal app as clean as an empty canvas
Error downloading and extracting template package: TypeError: Cannot read properties of null (reading '0')
✖ Something went wrong while downloading and extracting the template.
Can't read JSON file: /home/ntpl/Documents/tutorial/native/newapp/app.json
└─ Cause: Error: ENOENT: no such file or directory, open '/home/ntpl/Documents/tutorial/native/newapp/app.json'
├─ readAsync /usr/local/lib/node_modules/expo-cli/node_modules/#expo/json-file/src/JsonFile.ts:158:13
├─ extractAndPrepareTemplateAppAsync /usr/local/lib/node_modules/expo-cli/src/commands/utils/extractTemplateAppAsync.ts:25:25
└─ actionAsync /usr/local/lib/node_modules/expo-cli/src/commands/initAsync.ts:287:19
Does anyone know how to solve this?
try this:
npm cache clean --force
npm fund
npm audit fix --force
npm i --package-lock-only
npm audit fix --force
New to Node and NPM and trying to play around with babylon.js. I installed NVM and switched to Node 16 using nvm use 16. Then I upgraded NPM via npm install -g npm#8.7.0. So far so good.
Then, just like the docs say, I attempt to install the Babylon modules:
npm install babylonjs --save
However the output for this command is:
npm WARN deprecated source-map-url#0.4.1: See https://github.com/lydell/source-map-url#deprecated
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 source-map-resolve#0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
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 chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
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 chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated html-webpack-plugin#3.2.0: 3.x is no longer supported
npm WARN deprecated svgo#1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
added 952 packages, removed 4 packages, changed 31 packages, and audited 1162 packages in 34s
87 packages are looking for funding
run `npm fund` for details
21 vulnerabilities (8 moderate, 12 high, 1 critical)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
I would expect to see a friendly message that says something like:
"The babylonjs modules have been successfully installed"
That's the type of message you'd get using a mature build system such as Maven or Gradle. Or, if it failed, I'd expect to see something like:
"Failure: NPM failed to install the modules because of X"
But instead I see a bunch of unsettling versioning/security (vulnerabilities detected) warnings and a message that reads:
To address all issues, run:
npm audit fix
Run `npm audit` for details.
This leaves me with several unsettling feelings. The main question here is: Did the command succeed? Are the babylonjs modules installed? Did they install correctly? How can I tell? My current directory is still empty...
However, as an aside: do I need to be concerned about all of these warnings? Did they prevent the babylonjs modules from installing properly?
With Maven or Gradle, it will tell you (clear as day) whether your CLI invocation failed or succeeded, but this output is neither.
Don't worry, the installation did occur and from the looks of it, it was successful.
Everything else you are seeing is as a result of the interconnectedness and vastness of the npm ecosystem. The warnings at the top refer to nested dependencies of babylon.js, which may have been deprecated in favour of other modules. There is nothing you can do about this.
However, if you are feeling very keen and you know the authors whose libraries depend on these deprecated ones, you can ask them (nicely) to release new versions of their package without those deprecated packages; Then ask the authors babylon.js (once again, nicely) to upgrade their dependencies to the version released by those authors.
tl;dr
The warnings about vulnerabilities, followed by the command (npm audit fix) to fix them is probably the most you can do just to be safe. Run the command and continue your work.
npm:the version of expo doesnot come.I will thanful if u could solve my problem
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated graphql-tools#3.0.0: This package has been deprecated and now it only exports makeExecutableSchema.\nAnd it will no longer receive updates.\nWe recommend you to migrate to scoped packages such as #graphql-tools/schema, #graphql-tools/utils and etc.\nCheck out https://www.graphql-tools.com to learn what package you should use instead```
changed 1710 packages, and audited 1711 packages in 8m
110 packages are looking for funding
run `npm fund` for details
23 vulnerabilities (20 moderate, 3 high)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
.........................
<>
Lees-MacBook-Air-2:~ yuanhuilee$ node -v
v16.4.2
Lees-MacBook-Air-2:~ yuanhuilee$ npm -v
7.18.1
Lees-MacBook-Air-2:~ yuanhuilee$ sudo npm install -g cordova ionic
Password:
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated ionic#5.4.16: The Ionic CLI now uses ✨ #ionic/cli ✨ for its package name! 👉 https://twitter.com/ionicframework/status/1223268498362851330
changed 716 packages, and audited 717 packages in 23s
42 packages are looking for funding
run `npm fund` for details.
Any idea what error might this be? I am trying to install ionic framework on my Mac laptop. Thank you.
You should read the error logs, it's literally telling you what you need to do:
https://twitter.com/ionicframework/status/1223268498362851330
Uninstall old Ionic CLI
npm uninstall -g ionic
Install new Ionic CLI
npm install -g #ionic/cli