Mupx deployment fails. Why? - javascript

I'm trying to deploy Telescope to a simple Ubuntu 16.04 server. So I'm using the suggested deployment with MupX. After setting up the mup.json file, I did a mupx deploy:
$ mupx setup
Meteor Up: Production Quality Meteor Deployments
------------------------------------------------
Configuration file : mup.json
Settings file : settings.json
Started TaskList: Setup (linux)
[146.185.181.9] - Installing Docker
[146.185.181.9] - Installing Docker: SUCCESS
[146.185.181.9] - Setting up Environment
[146.185.181.9] - Setting up Environment: SUCCESS
[146.185.181.9] - Copying MongoDB configuration
[146.185.181.9] - Copying MongoDB configuration: SUCCESS
[146.185.181.9] - Installing MongoDB
[146.185.181.9] - Installing MongoDB: SUCCESS
No problems there, so after this I tried a mupx deploy, but that ends with an error:
$ mupx deploy
Meteor Up: Production Quality Meteor Deployments
------------------------------------------------
Configuration file : mup.json
Settings file : settings.json
Meteor app path : /Users/kramer65/dev/repos/Telescope
Using buildOptions : {}
nova:rss: updating npm dependencies -- rss...
Changes to your project's package version selections:
reactrouter:react-router-ssr downgraded from 3.1.4 to 3.1.3
Started TaskList: Deploy app 'telescope' (linux)
[146.185.181.9] - Uploading bundle
[146.185.181.9] - Uploading bundle: SUCCESS
[146.185.181.9] - Sending environment variables
[146.185.181.9] - Sending environment variables: SUCCESS
[146.185.181.9] - Initializing start script
[146.185.181.9] - Initializing start script: SUCCESS
[146.185.181.9] - Invoking deployment process
[146.185.181.9] - Invoking deployment process: SUCCESS
[146.185.181.9] - Verifying deployment
[146.185.181.9] x Verifying deployment: FAILED
-----------------------------------STDERR-----------------------------------
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
-----------------------------------STDOUT-----------------------------------
To see more logs type 'mup logs --tail=50'
----------------------------------------------------------------------------
So I checked what the logs said:
$ mupx logs --tail=50
Meteor Up: Production Quality Meteor Deployments
------------------------------------------------
Configuration file : mup.json
Settings file : settings.json
[146.185.181.9] at fileEvaluate (packages/modules-runtime/.npm/package/node_modules/install/install.js:141:1)
[146.185.181.9] at require (packages/modules-runtime/.npm/package/node_modules/install/install.js:75:1)
[146.185.181.9] at packages/react-meteor-data/createContainer.jsx:10:16
[146.185.181.9] npm WARN deprecated This version of npm lacks support for important features,
[146.185.181.9] npm WARN deprecated such as scoped packages, offered by the primary npm
[146.185.181.9] npm WARN deprecated registry. Consider upgrading to at least npm#2, if not the
[146.185.181.9] npm WARN deprecated latest stable version. To upgrade to npm#2, run:
[146.185.181.9] npm WARN deprecated
[146.185.181.9] npm WARN deprecated npm -g install npm#latest-2
[146.185.181.9] npm WARN deprecated
[146.185.181.9] npm WARN deprecated To upgrade to the latest stable version, run:
[146.185.181.9] npm WARN deprecated
[146.185.181.9] npm WARN deprecated npm -g install npm#latest
[146.185.181.9] npm WARN deprecated
[146.185.181.9] npm WARN deprecated (Depending on how Node.js was installed on your system, you
[146.185.181.9] npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
[146.185.181.9] npm WARN deprecated on Windows, run them from an Administrator prompt.)
[146.185.181.9] npm WARN deprecated
[146.185.181.9] npm WARN deprecated If you're running the version of npm bundled with
[146.185.181.9] npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
[146.185.181.9] npm WARN deprecated will be bundled with a version of npm#2, which has some small
[146.185.181.9] npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
[146.185.181.9] npm WARN deprecated semver behavior.
[146.185.181.9] npm WARN package.json meteor-dev-bundle#0.0.0 No description
[146.185.181.9] npm WARN package.json meteor-dev-bundle#0.0.0 No repository field.
[146.185.181.9] npm WARN package.json meteor-dev-bundle#0.0.0 No README data
[146.185.181.9] npm WARN cannot run in wd meteor-dev-bundle#0.0.0 node npm-rebuild.js (wd=/bundle/bundle/programs/server)
[146.185.181.9] => Starting meteor app on port:80
[146.185.181.9] WARNING: npm peer requirements (for react-meteor-data) not installed:
[146.185.181.9] - react#15.x not installed.
[146.185.181.9] - react-addons-pure-render-mixin#15.x not installed.
[146.185.181.9]
[146.185.181.9] Read more about installing npm peer dependencies:
[146.185.181.9] http://guide.meteor.com/using-packages.html#peer-npm-dependencies
[146.185.181.9]
[146.185.181.9]
[146.185.181.9] /bundle/bundle/programs/server/node_modules/fibers/future.js:267
[146.185.181.9] throw(ex);
[146.185.181.9] ^
[146.185.181.9] Error: Can't find npm module 'react'. Did you forget to call 'Npm.depends' in package.js within the 'modules-runtime' package?
[146.185.181.9] at Object.Npm.require (/bundle/bundle/programs/server/boot.js:195:17)
[146.185.181.9] at options.fallback (packages/modules-runtime/modules-runtime.js:21:1)
[146.185.181.9] at require (packages/modules-runtime/.npm/package/node_modules/install/install.js:81:1)
[146.185.181.9] at meteorInstall.node_modules.meteor.react-meteor-data.createContainer.jsx (packages/react-meteor-data/createContainer.jsx:5:1)
[146.185.181.9] at fileEvaluate (packages/modules-runtime/.npm/package/node_modules/install/install.js:141:1)
[146.185.181.9] at require (packages/modules-runtime/.npm/package/node_modules/install/install.js:75:1)
[146.185.181.9] at meteorInstall.node_modules.meteor.react-meteor-data.react-meteor-data.jsx (packages/react-meteor-data/react-meteor-data.jsx:7:25)
[146.185.181.9] at fileEvaluate (packages/modules-runtime/.npm/package/node_modules/install/install.js:141:1)
[146.185.181.9] at require (packages/modules-runtime/.npm/package/node_modules/install/install.js:75:1)
[146.185.181.9] at packages/react-meteor-data/createContainer.jsx:10:16
In these logs I read something about React not being installed. But as far as I can see, it installs Telescope into a Docker container, and I don't really know how I can install react within that container.
Does anybody have any idea what I can do to fix this?

Related

How can I install anything using npm if everything yields the same error?

Any time I try to install anything via npm, I get this warning:
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'tiletype#0.1.0',
npm WARN EBADENGINE required: { node: '0.8.x || 0.10.x' },
npm WARN EBADENGINE current: { node: 'v16.15.1', npm: '8.11.0' }
npm WARN EBADENGINE }
followed by this error (among several other less informative errors)
npm ERR! code 1
npm ERR! path /home/ubuntu/projects/GitHub/AWCPT/opentrees-data/node_modules/mbtiles/node_modules/sqlite3
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install --fallback-to-build
This includes npm install, npm install colors, npm install sqlite3, and npm install tiletype. How do I fix this?
There is clearly something wrong with the tiletype package.
It requires node v0.8.x or 0.10.x, while you're running v16.15.1.
On top of that, tiletype v0.1.0 is discontinued for quite a while.
Perhaps, deleting the node_modules folder and reinstalling all packages from scratch (npm i) would fix it.
If not, check where this package comes from. Is it in your package.json or is is installed as a dependency for another package?
Use nvm to switch to older version of node.
nvm install v0.10
nvm use v0.10
Delete node modules folder and install npm packages again
npm install

npm ERR! Windows_NT 10.0.19044 while installing library using npm

I am working on a project in our organization. while i am trying to run or install libraries it's getting an error.
E:\GIT\bookshelf>npm install
npm WARN deprecated bcrypt-nodejs#0.0.3: bcrypt-nodejs is no longer actively maintained. Please use bcrypt or bcryptjs
npm WARN deprecated #angular/http#4.1.3: Package no longer supported. Use #angular/common instead
npm WARN deprecated formidable#1.1.1: Please upgrade to latest, formidable#v2 or formidable#v3!
npm WARN deprecated core-js#2.4.1: core-js#<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated angular-tree-component#3.2.3: Library moved to #circlon/angular-tree-component
npm WARN deprecated multer#1.2.0: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated angular2-infinite-scroll#0.3.4: Please use the new --> ngx-infinite-scroll <--- supports in Angular +4, AOT compilation and optimized code bundle
npm WARN deprecated log4js#2.3.12: 2.x is no longer supported. Please upgrade to 6.x or higher.
npm WARN deprecated ckeditor#4.5.9: We have renamed the #ckeditor package. New versions are available under the #ckeditor4 name.
npm WARN deprecated angular2-recaptcha#0.6.0: Package no longer supported.
npm WARN deprecated fingerprintjs2#1.5.1: Package has been renamed to #fingerprintjs/fingerprintjs. Install #fingerprintjs/fingerprintjs to get updates.
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated request#2.83.0: request has been deprecated
npm ERR! Windows_NT 10.0.19044
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v6.17.1
npm ERR! npm v3.10.10
npm ERR! Cannot convert undefined or null to object
npm ERR!
npm ERR! If you need help, you may report this error at:
npm WARN deprecated ng2-bootstrap#1.4.0: ng2-bootstrap is renamed to ngx-bootstrap, please do npm i ngx-bootstrap -S
npm WARN deprecated request-promise#4.2.2: request-promise has been deprecated because it extends the now deprecated request package,
npm ERR! Please include the following file with any support request:
npm ERR! E:\GIT\bookshelf\npm-debug.log
I am using node version: 6.17.1 ( setup via NVM )
npm version: 3.10.10
windows machine.
Anyone helps me to find out what am I missing?
first remove package-json.lock file then try this npm command:
npm install --no-audit
run the command on your terminal.
or you can read this How can I fix this npm error? npm ERR! Windows_NT 10.0.19042, similar problem.

Unhandled exception occurred running ng serve

I'm not sure what it means or how to fix it. I just got a new machine and before I pulled down my repo, I installed the latest node, Angular Cli, npm and any other package/framework needed by my app. I cloned the repo and updated all local packages in my project to current versions using npm-check-updates. I then installed the updated packages with >npm install -force to resolve a couple of peer dependency issues. I'll post a screen shoot at the very bottom. But now ng serve doesn't run see error below. Not sure why?
➜ client git:(master) ✗ ng serve
⠋ Generating browser application bundles (phase: setup)...An unhandled exception occurred: Dev-server address info is not defined.
See "/private/var/folders/l6/zz0rl4793838rf924b4y0tqc0000gn/T/ng-5kND02/angular-errors.log" for further details.
➜ client git:(master) ✗
The error in the index.js file is from this below.
const devServer = createWebpackDevServer(webpackCompiler, devServerConfig);
devServer.startCallback(() => {
var _a;
const address = (_a = devServer.server) === null || _a === void 0 ? void 0 : _a.address();
if (!address) {
obs.error(new Error(`Dev-server address info is not defined.`));
return;
}
result = {
success: true,
port: typeof address === 'string' ? 0 : address.port,
family: typeof address === 'string' ? '' : address.family,
address: typeof address === 'string' ? address : address.address,
};
});
>npm install -force
➜ client git:(master) ✗ npm install -f
npm WARN using --force Recommended protections disabled.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ngx-gallery-9#1.0.6
npm WARN Found: tslib#2.3.1
npm WARN node_modules/tslib
npm WARN tslib#"^2.3.1" from the root project
npm WARN 22 more (#angular-devkit/build-angular, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer tslib#"^1.10.0" from ngx-gallery-9#1.0.6
npm WARN node_modules/ngx-gallery-9
npm WARN ngx-gallery-9#"^1.0.6" from the root project
npm WARN
npm WARN Conflicting peer dependency: tslib#1.14.1
npm WARN node_modules/tslib
npm WARN peer tslib#"^1.10.0" from ngx-gallery-9#1.0.6
npm WARN node_modules/ngx-gallery-9
npm WARN ngx-gallery-9#"^1.0.6" from the root project
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
npm WARN deprecated source-map-resolve#0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
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 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 tslint#6.1.3: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
added 1163 packages, and audited 1164 packages in 37s
118 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
I then installed the updated packages with npm install -force to resolve a couple of peer dependency issues.
Did you actually manually resolve all the issues or think that the command above would do it for you?
My guess is that the dependencies are not installed properly, but I can be wrong.
You might want to try the solution I just posted npm not installing unable to resolve dependency tree. I also included the link in the post for further troubleshooting.
This might be due to the old version of the node.
Kindly update your node version to the latest then run the following command.
sudo n lts
Then run the following command.
ng run serve
This might help you

Unable to install jasmine-core in npm Ubuntu

I'm having some problems to install Jasminejs. I'll really appreciate some help please. Thanks!
First I run this:
npm install karma-cli -g
I don't get any errors with this command.
After running this command:
npm install jasmine-core --save-dev
I'm getting this messages:
jasmine-core#2.4.1
UNMET PEER DEPENDENCY karma#
npm warn optional skipping failed optional dependency /chokidar/fsevents
npm warn notsup Not compatible with your operating system or architecture: fsevents#1.0.12
npm warn karma-jasmine#1.0.2 requires a peer of karma#* but none was installed.
npm warn karma phantomjs-launcher#1.0.0 requires a peer of karma#>=0.9 but none was installed
If I try to run this command:
npm install phantomjs-prebuilt --save
I' getting a similar error message. I'm using Ubuntu 14.04.4, Node 5.10.1 and npm 3.10.2 .
You met 'UNMET PEER DEPENDENCY' issue is because NPM3 no longer gets dependencies automatically. You should put missing dependency on the same install command line despite you have already installed the package.
e.g. npm install jasmine-core karma --save-dev

Issues installing Sails on Ubuntu && node v.4

I was wondering if anyone else has had problems installing sails in ubuntú vps with node v.4.
Thanks,
Marcos
root#marcoscorreia:/# sudo npm install sails
|
sails#0.11.0 preinstall /node_modules/sails
node ./lib/preinstall_npmcheck.js
Sails.js Installation: Checking npm-version successful
npm WARN deprecated grunt-lib-contrib#0.7.1: DEPRECATED. See readme:
https://github.com/gruntjs/grunt-lib-contrib
utf-8-validate#1.1.0 install /node_modules/sails/node_modules/sails-hook-
sockets/node_mod/socket.io/node_modules/engine.io/node_modules/ws/node_modu > les/utf-8-validate
node-gyp rebuild

Categories