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
Related
I am currently trying to connect Firebase to my React Native app that uses Expo. Im currently using this guide: https://docs.expo.io/guides/using-firebase/?fbclid=IwAR0c7g8a-005utr_ROomb_k3ptlAHel3kq004AtFbNkV9iWREeapzR0Dabg and it lead me to the github "Firebase JS SDK". I downloaded the whole github repo (https://github.com/firebase/firebase-js-sdk) and like tried following the instructions on the github such as downloading node, yarn, and java but I am confused on what to do next with the downloaded repo. I have tried running the command "npm install" to try and install the dependencies but I get this error:
npm WARN deprecated tslint#6.1.2: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request#2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
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 resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
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 mkdirp-promise#5.0.1: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
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 ERR! Unexpected end of JSON input while parsing near '...cMP/3jKIr36/huSPHVVgD'
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Ban-Jian\AppData\Roaming\npm-cache\_logs\2020-05-19T23_15_25_175Z-debug.log
And when I run the command: "yarn build" I get this error:
lerna ERR! yarn run build exited 2 in '#firebase/firestore'
lerna ERR! yarn run build stdout:
$ tsc -m es2015 --moduleResolution node scripts/*.ts
error TS6053: File 'scripts/*.ts' not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
lerna ERR! yarn run build stderr:
error Command failed with exit code 2.
lerna ERR! yarn run build exited 2 in '#firebase/firestore'
lerna WARN complete Waiting for 4 child processes to exit. CTRL-C to exit immediately.
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
I guess my question is: How do I properly set up the SDK I downloaded from the github?
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'
steps:
npm install -g yo
npm install -g grunt
npm install -g bower
npm install -g generator-angular
mkdir storefront
cd storefront/
yo angular
grunt serve
grunt serve isn't working for me as seen below:
ME$ grunt serve
Running "serve" task
Running "clean:server" (clean) task
>> 0 paths cleaned.
Running "wiredep:app" (wiredep) task
Running "wiredep:test" (wiredep) task
Running "wiredep:sass" (wiredep) task
Running "concurrent:server" (concurrent) task
Warning: Running "compass:server" (compass) task
Warning: Couldn't find the `compass` binary. Make sure it's installed and in your $PATH Use --force to continue.
Aborted due to warnings.
Execution Time (2015-04-08 20:14:01 UTC)
loading tasks 5ms ▇▇▇▇▇▇▇▇▇▇ 21%
compass:server 18ms ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 75%
Total 24ms Use --force to continue.
Aborted due to warnings.
Execution Time (2015-04-08 20:13:58 UTC)
wiredep:app 115ms ▇▇▇▇ 4%
concurrent:server 2.6s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 95%
Total 2.8s
I tried two things:
sudo npm install -g grunt-cli
that resulted in:
$ sudo npm install -g grunt-cli
Password:
/usr/local/bin/grunt -> /usr/local/lib/node_modules/grunt-cli/bin/grunt
npm WARN unmet dependency /usr/local/lib/node_modules/browserify/node_modules/module-deps/node_modules/through2 requires readable-stream#'~1.0.17' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/browserify/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.0.27-1
npm WARN unmet dependency /usr/local/lib/node_modules/meteorite/node_modules/prompt/node_modules/winston requires colors#'0.x.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/meteorite/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/phonegap-build requires colors#'0.6.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/connect-phonegap/node_modules/connect/node_modules/multiparty/node_modules/stream-counter requires readable-stream#'~1.1.8' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/connect-phonegap/node_modules/connect/node_modules/multiparty/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.1.13-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/prompt/node_modules/winston requires colors#'0.x.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
grunt-cli#0.1.13 /usr/local/lib/node_modules/grunt-cli
├── resolve#0.3.1
├── nopt#1.0.10 (abbrev#1.0.5)
└── findup-sync#0.1.3 (lodash#2.4.1, glob#3.2.11)
and
npm install -g compass
that resulted in:
ME$ npm install -g compass
npm WARN unmet dependency /usr/local/lib/node_modules/browserify/node_modules/module-deps/node_modules/through2 requires readable-stream#'~1.0.17' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/browserify/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.0.27-1
npm WARN unmet dependency /usr/local/lib/node_modules/meteorite/node_modules/prompt/node_modules/winston requires colors#'0.x.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/meteorite/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/phonegap-build requires colors#'0.6.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/connect-phonegap/node_modules/connect/node_modules/multiparty/node_modules/stream-counter requires readable-stream#'~1.1.8' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/connect-phonegap/node_modules/connect/node_modules/multiparty/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.1.13-1
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/prompt/node_modules/winston requires colors#'0.x.x' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/phonegap/node_modules/colors,
npm WARN unmet dependency which is version 0.6.0-1
compass#0.1.1 /usr/local/lib/node_modules/compass
What is wrong?
I had the same issue. I fixed it by setting logConcurrentOutput to false in my Gruntfile.
Go to app --> Gruntfile.js
Search for concurrent, and ensure your concurrent code for logConcurrentOutput looks like this:
concurrent: {
ionic: {
tasks: [],
options: {
logConcurrentOutput: false
}
}
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