I want to install Rocket.Chat and Meteor on Freebsd 10.3
Does anyone know why when running NPM through Meteor, it is failing to download and install the modules:
[rocketchat#web ~/meteor]$ ./meteor -v
meteor: updating npm dependencies -- meteor-deque...
Building package meteor |
/usr/home/rocketchat/meteor/dev_bundle/lib/node_modules/ip-regex /index.js:3
const word = '[a-fA-F\\d:]';
^^^^^
babel-compiler: updating npm dependencies -- meteor-babel...
ecmascript-runtime: updating npm dependencies -- meteor-ecmascript- runtime...
promise: updating npm dependencies -- meteor-promise...
npm-mongo: updating npm dependencies -- mongodb...
logging: updating npm dependencies -- cli-color...
xmlbuilder: updating npm dependencies -- xmlbuilder...
Errors prevented isopacket build:
While building package meteor:
error: Can't install npm dependencies. Are you connected to the internet?
While building package babel-compiler:
error: Can't install npm dependencies. Are you connected to the internet?
While building package ecmascript-runtime:
error: Can't install npm dependencies. Are you connected to the internet?
error: File not found: .npm/package/node_modules/meteor-ecmascript- runtime/client.js
While building package promise:
error: Can't install npm dependencies. Are you connected to the internet?
error: File not found: .npm/package/node_modules/meteor-promise /promise.bundle.js
Related
I have downloaded a full project that has been in use for about a year now, I got a new computer and am trying to upload a change to a function. I had errors and now I am trying to redeploy a function that I know works and is the same as the source in Google Cloud.
I run:
firebase deploy --only functions:generateThumbnail
and this is the output:
deploying functions
i functions: ensuring necessary APIs are enabled...
✔ functions: all necessary APIs are enabled
i functions: preparing functions directory for uploading...
Error: Error parsing triggers: Cannot find module './dnssec'
Try running "npm install" in your functions directory before deploying.
I run npm install:
npm WARN functions# requires a peer of eslint#2.x but none is installed. You must install peer dependencies yourself.
npm WARN ajv-keywords#3.2.0 requires a peer of ajv#^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN firebase-functions#0.8.2 requires a peer of firebase-admin#~5.10.0 but none is installed. You must install peer dependencies yourself.
audited 7867 packages in 6.019s
found 20 vulnerabilities (3 low, 17 moderate)
run `npm audit fix` to fix them, or `npm audit` for details
then I ran npm audit fix:
npm WARN functions# requires a peer of eslint#2.x but none is installed. You must install peer dependencies yourself.
npm WARN ajv-keywords#3.2.0 requires a peer of ajv#^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN firebase-functions#0.8.2 requires a peer of firebase-admin#~5.10.0 but none is installed. You must install peer dependencies yourself.
removed 1 package and updated 5 packages in 7.583s
fixed 8 of 20 vulnerabilities in 7867 scanned packages
2 package updates for 12 vulns involved breaking changes
(use `npm audit fix --force` to install breaking changes; or do it by hand)
..I am still getting the same error as before:
Error: Error parsing triggers: Cannot find module './dnssec'
Hey so I think this is an issue with npm not updating the packages correctly. I was running into the same error.
Error: Error parsing triggers: Cannot find module './dnssec'
I found that the dnssec resource is within the 'sshpk' node module folder. So in order to correct the error I just went into the node_modules folder of my functions directory and removed the 'sshpk' module, and while still in the functions directory ran 'npm install'. Hopefully this works for you and some other people running into this issue.
Cheers. Good luck!
npm WARN ajv-keywords#3.1.0 requires a peer 0f ajv#A6.0.0 but none is installed.
You must install peer dependencies yourself.
Install ajv package before running application. ajv-keywords need it first
What does these lines mean
meteor npm install --production
meteor npm install --save
?
The Docs explains the command meteor npm <pacakge name> So the npm package is install, but what does the flag --production and --save do?
The meteor npm command simply forwards the arguments that follow it to Meteor's bundled npm version, so it behaves as the npm command-line tool.
The basic command is meteor npm <command and arguments.
This basic install command is meteor npm install <package name> rather than meteor npm <package name>.
Its relevant documentation is therefore not the one you referenced in your question, but the npm's CLI tool's (you referenced npm's install package, note the npm install install there).
NPM creates a package.json file and lists the project's dependencies there. You use the --save flag to instruct npm to add the packages installed to the dependencies file and the --production flag to instruct npm to not install its dev-dependencies, which are dependencies that were used for developing and debugging this package, but are not strictly required for its operation in production.
Take the time to familiarize yourself with the tool.
From the CLI docs:
npm install (with no args, in package dir)
npm install [<#scope>/]<name>
npm install [<#scope>/]<name>#<tag>
npm install [<#scope>/]<name>#<version>
npm install [<#scope>/]<name>#<version range>
npm install <tarball file>
npm install <tarball url>
npm install <folder>
alias: npm i
common options: [-S|--save|-D|--save-dev|-O|--save-optional] [-E|--save-exact] [--dry-run]
-S, --save: Package will appear in your dependencies.
With the --production flag (or when the NODE_ENV environment variable is set to production), npm will not install modules listed in devDependencies.
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