mygame#4.1.0 start /usr/src/app
node server.js
Error: Cannot find module '#adonisjs/bodyparser/providers/BodyParserProvider'
Require stack:
/usr/src/app/node_modules/require-stack/src/index.js
/usr/src/app/node_modules/require-stack/index.js
/usr/src/app/node_modules/#adonisjs/fold/src/Ioc/index.js
/usr/src/app/node_modules/#adonisjs/fold/index.js
/usr/src/app/server.js
1 requireStack
/usr/src/app/node_modules/require-stack/src/index.js:44
2 anonymous
/usr/src/app/node_modules/#adonisjs/fold/src/Registrar/index.js:104
3 arrayMap
/usr/src/app/node_modules/lodash/lodash.js:653
4 Function.map
/usr/src/app/node_modules/lodash/lodash.js:9622
5 interceptor
/usr/src/app/node_modules/lodash/lodash.js:17094
6 thru
/usr/src/app/node_modules/lodash/lodash.js:8859
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mygame#4.1.0 start: node server.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mygame#4.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/node/.npm/_logs/2021-03-25T00_06_01_885Z-debug.log
The problem is npm is installing the wrong version from body-parser, due to a recent push.
As a workaround:
go to package.json
you can replace the ^ with ~
"#adonisjs/bodyparser": "~2.0.9",
Since we prefixed the version with ~, NPM retrieved the latest patch version under the 2.0.9 minor version, which turned out to be 2.0.9 itself
For more info: https://github.com/adonisjs/bodyparser/issues/43
Related
I'm just trying to create a new app from scratch, but getting this error:
Command failed with exit code 1: npm install --loglevel error
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: ember-sample#0.0.0
npm ERR! Found: ember-cli#4.3.0
npm ERR! node_modules/ember-cli
npm ERR! dev ember-cli#"~4.3.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer ember-cli#"~3.2.0" from ember-cli-dependency-checker#3.3.0
npm ERR! node_modules/ember-cli-dependency-checker
npm ERR! dev ember-cli-dependency-checker#"^3.2.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
These are the repro steps:
open command prompt in Win11.
install ember
npm install -g ember-cli
create app ember-sample
ember new ember-sample
and just after that I get the error above.
Could I be missing anything? I have already installed node v16.14.2, npm 8.5.0, ember-cli: 4.3.0
I was already taking a look on ember.js official website
Actually Ember CLI is Compatible with NodeVersion 12. You might be using a later node versio like 14 or 16. My problem is solved when I downgraded to Node 12 lts
A fix is on its way. You could follow what #NullVoxPopuli said in the comments.
https://github.com/quaertym/ember-cli-dependency-checker/issues/132
I am using libpostal for address parsing.Here is the git link: https://github.com/pasupulaphani/libpostal-docker
This docker image runs perfectly fine on my local machine but once I try and run it on EC2 it fails with below error.
Killed
npm ERR! Linux 4.14.138-114.102.amzn2.x86_64
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v7.10.0
npm ERR! npm v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! node-zeromq#1.0.0 start: `DEBUG=libpostal:zeromq* node server.js`
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the node-zeromq#1.0.0 start script 'DEBUG=libpostal:zeromq* node server.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-zeromq package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! DEBUG=libpostal:zeromq* node server.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-zeromq
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-zeromq
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /root/.npm/_logs/2019-10-03T00_30_06_303Z-debug.log
I did reinstall the latest versions of zerorpc, nodejs and npm on the EC2 instance. But still cannot figure out the error.
nvm_tree_contains_path /home/pipeline/.nvm /home/pipeline/.nvm/versions/node/v8.15.1
'[' -n 'Now using node v8.15.1 (npm v6.4.1)' ']'
nvm_echo 'Now using node v8.15.1 (npm v6.4.1)'
command printf '%s\n' 'Now using node v8.15.1 (npm v6.4.1)'
node -v
Now using node v8.15.1 (npm v6.4.1)
npm -v
v8.15.1
6.4.1
test_contracts
for CONTRACT in '${CONTRACTS}'
test_contract iot-blockchain-perishable-network
CONTRACT=iot-blockchain-perishable-network
'[' -f contracts/iot-blockchain-perishable-network/package.json ']'
test_composer_contract iot-blockchain-perishable-network
CONTRACT=iot-blockchain-perishable-network
echo testing composer contract iot-blockchain-perishable-network
pushd contracts/iot-blockchain-perishable-network
npm test
testing composer contract iot-blockchain-perishable-network
~/bc70ab6b-afeb-4ddf-a8ee-ddb7b7e23ce1/contracts/iot-blockchain-perishable-network ~/bc70ab6b-afeb-4ddf-a8ee-ddb7b7e23ce1
perishable-network#0.2.6-deploy.2 pretest /home/pipeline/bc70ab6b-afeb-4ddf-a8ee-ddb7b7e23ce1/contracts/iot-blockchain-perishable-network
npm run lint
perishable-network#0.2.6-deploy.2 lint /home/pipeline/bc70ab6b-afeb-4ddf-a8ee-ddb7b7e23ce1/contracts/iot-blockchain-perishable-network
eslint .
sh: 1: eslint: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! perishable-network#0.2.6-deploy.2 lint: eslint .
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the perishable-network#0.2.6-deploy.2 lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pipeline/.npm/_logs/2019-03-06T14_37_44_449Z-debug.log
npm ERR! Test failed. See above for more details.
Finished: FAILED
You will just need to run npm install and see if everything was successfully installed. Because the project will run inside IBM Blockchain, you dont need to run it locally.
For a more detailed information on how to achieve your gold, check this answer:
https://stackoverflow.com/a/55358606/7004017
I have tried to implement laravel passport authentication in my project, but it's not working. Initially, i have installed laravel5.5 with other configuration and file permissions all the stuff.
To implement passport authentication I have followed laravel documentation Document Url
Following steps, I have done,
composer require laravel/passport
php artisan migrate
php artisan passport:install
I have added this line App\User
use Laravel\Passport\HasApiTokens;
use HasApiTokens, Notifiable;
Routes Added in AuthServiceProvider file inside the boot function
Passport::routes();
Inside the config/auth.php file, I have changed API driver as passport
php artisan vendor:publish --tag=passport-components
Inside this file resources/assets/js/app.js
Vue.component(
'passport-clients',
require('./components/passport/Clients.vue')
);
Vue.component(
'passport-authorized-clients',
require('./components/passport/AuthorizedClients.vue')
);
Vue.component(
'passport-personal-access-tokens',
require('./components/passport/PersonalAccessTokens.vue')
);
npm run dev
When running this command I'm getting an error
$ npm run dev
# dev /var/www/html/local/laravel5.5
npm run development
# development /var/www/html/local/laravel5.5
cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
sh: 1: cross-env: not found
npm ERR! Linux 4.4.0-98-generic
npm ERR! argv "/home/sysadmin/.nvm/versions/node/v6.11.1/bin/node" "/home/sysadmin/.nvm/versions/node/v6.11.1/bin/npm" "run" "development"
npm ERR! node v6.11.1
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! # development: cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the # development script 'cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /var/www/html/local/laravel5.5/npm-debug.log
npm ERR! Linux 4.4.0-98-generic
npm ERR! argv "/home/sysadmin/.nvm/versions/node/v6.11.1/bin/node" "/home/sysadmin/.nvm/versions/node/v6.11.1/bin/npm" "run" "dev"
npm ERR! node v6.11.1
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! # dev: npm run development
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # dev script 'npm run development'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm run development
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /var/www/html/local/laravel5.5/npm-debug.log
You must run in cmd/terminal, from your project folder
npm install --save
and then
npm run dev
I've been using Zurb Foundation for Emails successfully for quite some time. Suddenly the build process is failing.
I updated to Node 7.7.2 and NPM 4.1.2, deleted the node_modules directory and ran npm install to reinstall the dependencies, but it didn't solve the issue.
$ npm run build
foundation-emails-template#1.0.0 build /Users/[REDACTED]
gulp --production
[12:46:56] Requiring external module babel-register
[12:46:57] Using gulpfile ~/[REDACTED]/gulpfile.babel.js
[12:46:57] Starting 'default'...
[12:46:57] Starting 'build'...
[12:46:57] Starting 'clean'...
[12:46:57] Finished 'clean' after 11 ms
[12:46:57] Starting 'pages'...
[12:46:59] Finished 'pages' after 1.32 s
[12:46:59] Starting 'sass'...
[12:47:05] 'sass' errored after 6.91 s
[12:47:05] Error in plugin 'gulp-uncss'
Message:
Unexpected EOF
Details:
domainEmitter: [object Object]
domain: [object Object]
domainThrown: false
[12:47:05] 'build' errored after 8.25 s
[12:47:05] 'default' errored after 8.25 s
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v7.7.2
npm ERR! npm v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! foundation-emails-template#1.0.0 build: `gulp --production`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the foundation-emails-template#1.0.0 build script 'gulp --production'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the foundation-emails-template package,
npm ERR! not with npm itself.
Or if I try to run gulp --production by itself:
$ gulp --production
[12:29:38] Requiring external module babel-core/register
[12:29:39] Using gulpfile ~/[REDACTED]/gulpfile.babel.js
/usr/local/lib/node_modules/gulp/bin/gulp.js:129
gulpInst.start.apply(gulpInst, toRun);
^
TypeError: Cannot read property 'apply' of undefined
at /usr/local/lib/node_modules/gulp/bin/gulp.js:129:19
at _combinedTickCallback (internal/process/next_tick.js:73:7)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)
npm start works as expected; I just can't inline the styles.
Any ideas? TIA.
It's because the node environment had changed.
Run this in your console:
npm rebuild node-sass
npm rebuild gulp-uncss
It should fix the issue.
I got the same error and was caused by a code-specific issue so make sure all your code is valid. In my case I was missing a closing " on a class.