1.
D:\Firebase>npm install firebase-functions#latest firebase-admin#latest --save
firebase-functions#2.0.5 postinstall D:\Firebase\node_modules\firebase-functions
node ./upgrade-warning
======== WARNING! ========
This upgrade of firebase-functions contains breaking changes if you are upgrading from a version below v1.0.0.
To see a complete list of these breaking changes, please go to:
https://firebase.google.com/docs/functions/beta-v1-diff
npm WARN saveError ENOENT: no such file or directory, open 'D:\Firebase\package.json'
- mime-db#1.35.0 node_modules\compressible\node_modules\mime-db
- mime-db#1.35.0 node_modules\request\node_modules\mime-db
- mime-types#2.1.19 node_modules\request\node_modules\mime-types
D:\Firebase
+-- firebase-admin#6.0.0
| +-- #google-cloud/storage#1.7.0
| | +-- compressible#2.0.14
| | | `-- mime-db#1.35.0
| | `-- mime-types#2.1.19
| `-- #types/node#8.10.26
`-- firebase-functions#2.0.5
npm WARN enoent ENOENT: no such file or directory, open 'D:\Firebase\package.json'
npm WARN Firebase No description
npm WARN Firebase No repository field.
npm WARN Firebase No README data
npm WARN Firebase No license field.
D:\Firebase\functions>npm install --save firebase-functions#latest
firebase-functions#2.0.5 postinstall D:\Firebase\functions\node_modules\firebase-functions
node ./upgrade-warning
======== WARNING! ========
This upgrade of firebase-functions contains breaking changes if you are upgrading from a version below v1.0.0.
To see a complete list of these breaking changes, please go to:
https://firebase.google.com/docs/functions/beta-v1-diff
functions# D:\Firebase\functions
+-- UNMET PEER DEPENDENCY firebase-admin#5.12.0
`-- firebase-functions#2.0.5
npm WARN firebase-functions#2.0.5 requires a peer of firebase-admin#~6.0.0 but none was installed.
~
I check "package.json"
"dependencies": {
"firebase-admin": "~5.12.0",
"firebase-functions": "^2.0.5"
},
How can I update from firebase-admin#5.12.0 to firebase-admin#6.0.0 ?
Thanks very much.
To get the latest version of any npm module for your Cloud Functions project:
cd functions
npm install firebase-admin#latest
In my case, I kept running npm install and npm install firebase-admin#latest (as suggested in the warning message itself) under /[project]/functions and getting the same warning.
I realized I had forgotten to run this update:
npm install --save firebase-functions#latest
Related
I install firebase-tools with npm
but terminal can't find firebase-tools :(...
also I tried auto installing script "curl -sL https://firebase.tools | bash" but this also give me this error "This tool has encountered an error."
what should i do?
KangTaeui-MacBook-Pro-2:practice_react kangtaegeun$ sudo npm install firebase-tools -g
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
/Users/kangtaegeun/.npm-global/bin/firebase -> /Users/kangtaegeun/.npm-global/lib/node_modules/firebase-tools/lib/bin/firebase.js
> protobufjs#6.10.1 postinstall /Users/kangtaegeun/.npm-global/lib/node_modules/firebase-tools/node_modules/protobufjs
> node scripts/postinstall
+ firebase-tools#8.9.0
added 593 packages from 364 contributors in 32.084s
KangTaeui-MacBook-Pro-2:practice_react kangtaegeun$ firebase
-bash: /usr/local/bin/firebase: No such file or directory
KangTaeui-MacBook-Pro-2:practice_react kangtaegeun$
when i'm typing this line in the git bash
npm install grunt-contrib-imagemin --save-dev
i get this errors
npm WARN saveError ENOENT: no such file or directory, open'C:\Users\hussa\package.json'
C:\Users\hussa
`-- grunt-contrib-imagemin#1.0.1
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\hussa\package.json'
npm WARN hussa No description
npm WARN hussa No repository field.
npm WARN hussa No README data
npm WARN hussa No license field.
You are telling npm to update your package.json file with the new dependency when using the --save-dev flags
Looks like you dont have a package.json file in your current directory. In which case you can create one with npm init and then rerun the npm install command after it is created.
If you do have a package.json file check you have permissions to edit and ensure it is not corrupt.
I have been trying to install arduino nodes in Node-Red through node-red-node-arduino following Node-Red's own guide (https://nodered.org/docs/hardware/arduino) to no avail. The node is marked as installed in the "Manage Palletes" tab, but it's disabled and refuses to enable itself. I tried to insert the sample code of the link above, but Node-Red doesn't recognize it. I installed the package arduino-firmata and node-red-node-serialport, and all the packages both locally (~/.node-red/node_modules) and globally (through -g option in npm), but the situation remains the same.
cd ~/.node-red
npm install node-red-node-arduino
npm install arduino-firmata
npm install node-red-node-serialport
sudo npm -g install node-red-node-arduino
sudo npm -g install arduino-firmata
sudo npm -g install node-red-node-serialport
They do spit out some weird logs, though, at least when installing locally.
> serialport#4.0.3 install /home/myusername/.node-red/node_modules/serialport
> node-pre-gyp install --fallback-to-build
[serialport] Success: "/home/myusername/.node-red/node_modules/serialport/build/Release/serialport.node" is installed via remote
/home/myusername/.node-red
├── arduino-firmata#0.3.4
├── node-red-node-arduino#0.0.9
├── node-red-node-serialport#0.4.0
└── serialport#4.0.3
npm WARN enoent ENOENT: no such file or directory, open '/home/myusername/.node-red/package.json'
npm WARN .node-red No description
npm WARN .node-red No repository field.
npm WARN .node-red No README data
npm WARN .node-red No license field.
npm WARN In serialport#4.0.3 replacing bundled version of minimist with minimist#0.0.8
npm WARN In serialport#4.0.3 replacing bundled version of abbrev with abbrev#1.0.9
npm WARN In serialport#4.0.3 replacing bundled version of delegates with delegates#1.0.0
...
Here is the log that shows up when running node-red in the terminal.
[warn] [arduino] Error: Cannot find module 'firmata/node_modules/serialport'
I have a Meteor + React app that works fine locally. I've tested using the --production flag and there are no issues.
Once I use mupx to deploy to my server, the deployment is successful but when I go to the deployed app it throws "There is no route for the path: /".
My routes.js file is located in the client directory.
Here is my mupx logs -f result
npm WARN deprecated This version of npm lacks support for important
features, npm WARN deprecated such as scoped packages, offered by the
primary npm npm WARN deprecated registry. Consider upgrading to at
least npm#2, if not the npm WARN deprecated latest stable version. To
upgrade to npm#2, run: npm WARN deprecated npm WARN deprecated npm -g
install npm#latest-2 npm WARN deprecated npm WARN deprecated To
upgrade to the latest stable version, run: npm WARN deprecated npm
WARN deprecated npm -g install npm#latest npm WARN deprecated npm
WARN deprecated (Depending on how Node.js was installed on your
system, you npm WARN deprecated may need to prefix the preceding
commands with sudo, or if npm WARN deprecated on Windows, run them
from an Administrator prompt.) npm WARN deprecated npm WARN
deprecated If you're running the version of npm bundled with npm WARN
deprecated Node.js 0.10 LTS, be aware that the next version of 0.10
LTS npm WARN deprecated will be bundled with a version of npm#2, which
has some small npm WARN deprecated backwards-incompatible changes made
to npm run-script and npm WARN deprecated semver behavior. npm WARN
package.json meteor-dev-bundle#0.0.0 No description npm WARN
package.json meteor-dev-bundle#0.0.0 No repository field. npm WARN
package.json meteor-dev-bundle#0.0.0 No README data
fibers#1.0.8 install
/bundle/bundle/programs/server/node_modules/fibers node build.js ||
nodejs build.js make: Entering directory
/bundle/bundle/programs/server/node_modules/fibers/build' CXX(target)
Release/obj.target/fibers/src/fibers.o CXX(target)
Release/obj.target/fibers/src/coroutine.o CC(target)
Release/obj.target/fibers/src/libcoro/coro.o SOLINK_MODULE(target)
Release/obj.target/fibers.node SOLINK_MODULE(target)
Release/obj.target/fibers.node: Finished COPY Release/fibers.node
make: Leaving
directory/bundle/bundle/programs/server/node_modules/fibers/build'
Installed in
/bundle/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.14/fibers.node
npm WARN cannot run in wd meteor-dev-bundle#0.0.0 node npm-rebuild.js
(wd=/bundle/bundle/programs/server) ansi-regex#0.2.1
node_modules/ansi-regex
ansi-styles#1.1.0 node_modules/ansi-styles
escape-string-regexp#1.0.5 node_modules/escape-string-regexp
chalk#0.5.1 node_modules/chalk
has-ansi#0.1.0 node_modules/has-ansi
strip-ansi#0.3.0 node_modules/strip-ansi
supports-color#0.2.0 node_modules/supports-color
eachline#2.3.3 node_modules/eachline
type-of#2.0.1 node_modules/type-of
amdefine#1.0.0 node_modules/amdefine
asap#2.0.3 node_modules/asap
underscore#1.5.2 node_modules/underscore
meteor-promise#0.5.1 node_modules/meteor-promise
promise#7.0.4 node_modules/promise
source-map-support#0.3.2 node_modules/source-map-support
semver#4.1.0 node_modules/semver
source-map#0.1.32 node_modules/source-map
fibers#1.0.8 node_modules/fibers
=> Starting meteor app on port:80
I cannot get grunt to work at all on Windows 7. Following the instructions on the Grunt website (http://gruntjs.com/getting-started) I've run:
npm uninstall -g grunt-cli
npm uninstall grunt
npm uninstall -g grunt-init
git clone git#github.com:gruntjs/grunt-init-jquery.git c:/Users/me/.grunt-init/jquery
npm install -g grunt-cli
grunt-init jquery
npm install .
After that, running "grunt" produces the following output:
grunt-cli: The grunt command line interface. (v0.1.9)
Fatal error: Unable to find local grunt.
If you're seeing this message, either a Gruntfile wasn't found or grunt
hasn't been installed locally to your project. For more information about
installing and configuring grunt, please see the Getting Started guide:
http://gruntjs.com/getting-started
The output of npm list grunt is:
npm WARN package.json consolidate#0.9.1 No repository field.
npm WARN package.json jquery-plugin#0.0.0-ignored No repository field.
npm WARN package.json passport-local-examples-login#0.0.0 No repository field.
npm WARN package.json receiptly#0.0.1 No repository field.
npm WARN package.json cookie-signature#1.0.1 No repository field.
npm WARN package.json fresh#0.1.0 No repository field.
npm WARN package.json methods#0.0.1 No repository field.
npm WARN package.json range-parser#0.0.4 No repository field.
npm WARN package.json send#0.1.0 No repository field.
npm WARN package.json pause#0.0.1 No repository field.
npm WARN package.json policyfile#0.0.4 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json eyes#0.1.8 No repository field.
npm WARN package.json bytes#0.2.0 No repository field.
npm WARN package.json dateformat#1.0.2-1.2.3 No repository field.
npm WARN package.json uid2#0.0.2 No repository field.
C:\Users\me\AppData\Roaming\npm
└─┬ grunt-init#0.2.1
└── grunt#0.4.1
Running "npm install grunt" in the current directory gives the same error when running grunt.
Any thoughts? My understanding is that grunt-cli is meant to look for a local grunt install, but I can't work out why it can't find it.
I know its been 2 years since this question was asked. However if someone wants in future:
I got the exact same issue. And I got this fixed by installing grunt locally. As per grunt site,
Note that installing grunt-cli does not install the Grunt task runner!
The job of the Grunt CLI is simple: run the version of Grunt which has
been installed next to a Gruntfile. This allows multiple versions of
Grunt to be installed on the same machine simultaneously.
So I just got it working by installing Grunt locally.
npm install grunt --save-dev
--save : adds it to your package.json.
-dev: adds it as a dev dependency.
There must be a Gruntfile.js located in the directory you run the command from. Also double check that 'npm install grunt' actually gave you a node_modules directory with a sub directory called grunt.
You should install grunt in GUI mode.
Open node.js cmd prompt then open the root folder and run the below commands
npm install ( once it done you can able to see node_modules folder in the root folder)
npm install –g grunt-cli (change the version from ("version": "minified" to Current release("version":"1.11"); you should replace with minified once you run build)
grunt build:full
Note: Version has to change when running grunt very first time.
if the above answer do not works then you can try by using this
rm -rf node_modules/ && npm cache clean && npm install