enter image description here> # dev C:\xampp\htdocs\laravel9_basic\basic
vite
internal/process/esm_loader.js:74
internalBinding('errors').triggerUncaughtException(
^
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. Received protocol 'node:'
at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:756:11)
at Loader.resolve (internal/modules/esm/loader.js:85:40)
at Loader.getModuleJob (internal/modules/esm/loader.js:229:28)
at ModuleWrap. (internal/modules/esm/module_job.js:51:40)
at link (internal/modules/esm/module_job.js:50:36) {
code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! # dev: vite
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # dev 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! C:\Users\Sudha\AppData\Roaming\npm-cache_logs\2022-07-23T13_50_47_419Z-debug.log
Related
We have a react native app and we configured it with Jenkins for CI/CD .While running the npm install command via Jenkins from the build window (execute shell) its getting failed .
Am using node : v10.16.3 and npm : 6.9.0 with latest jenkins version.
This is the logs for the last run
15:52:30 [cavionnovus-IOS] $ /bin/sh -xe /Users/Shared/Jenkins/tmp/jenkins5253804416691912910.sh
15:52:30 + export PATH=/usr/local/bin
15:52:30 + PATH=/usr/local/bin
15:52:30 + npm install
15:52:34 npm WARN deprecated deep-assign#3.0.0: Check out `lodash.merge` or `merge-options` instead.
15:52:36 npm WARN deprecated core-js#1.2.7: core-js#<2.6.8 is no longer maintained. Please, upgrade to core-js#3 or at least to actual version of core-js#2.
15:52:40 npm WARN deprecated left-pad#1.3.0: use String.prototype.padStart()
15:53:47
15:53:47 > fsevents#1.2.9 install /Users/Shared/Jenkins/Home/workspace/cavionnovus-IOS/node_modules/fsevents
15:53:47 > node install
15:53:47
15:53:47
15:53:47 > grpc#1.23.3 install /Users/Shared/Jenkins/Home/workspace/cavionnovus-IOS/node_modules/grpc
15:53:47 > node-pre-gyp install --fallback-to-build --library=static_library
15:53:47
15:53:48 npm WARN react-navigation-stack#1.9.4 requires a peer of react-native-screens#^1.0.0 || ^1.0.0-alpha but none is installed. You must install peer dependencies yourself.
15:53:48 npm WARN react-navigation-drawer#2.2.2 requires a peer of react-native-screens#^1.0.0 || ^1.0.0-alpha but none is installed. You must install peer dependencies yourself.
15:53:48 npm WARN eslint-plugin-react#7.12.4 requires a peer of eslint#^3.0.0 || ^4.0.0 || ^5.0.0 but none is installed. You must install peer dependencies yourself.
15:53:48 npm WARN eslint-plugin-react-native#3.6.0 requires a peer of eslint#^3.17.0 || ^4 || ^5 but none is installed. You must install peer dependencies yourself.
15:53:48 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.9 (node_modules/fsevents):
15:53:48 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.9 install: `node install`
15:53:48 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: spawn sh ENOENT
15:53:48
15:53:48 npm ERR! file sh
15:53:48 npm ERR! path sh
15:53:48 npm ERR! code ELIFECYCLE
15:53:48 npm ERR! errno ENOENT
15:53:48 npm ERR! syscall spawn sh
15:53:48 npm ERR! grpc#1.23.3 install: `node-pre-gyp install --fallback-to-build --library=static_library`
15:53:48 npm ERR! spawn sh ENOENT
15:53:48 npm ERR!
15:53:48 npm ERR! Failed at the grpc#1.23.3 install script.
15:53:48 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
There wont be any issues while running the same on windows machine , the isssue not there while running the npm commands from the jenkins workspace manualy .
So from the logs i think jenkins blocking creating new process from the build .
while running the command manually we could see that the dependency grpc is downloaded via remotely . that may be a new process and jenkin blocks / kill that child process.
This is the command i used on the build window of Jenkin
export PATH=/usr/local/bin
$sudo npm install
please help me to get ride of this issue .
suma#ubuntu:~/poc/land$ composer network start --networkName property-network --networkVersion 0.2.6-deploy.113 --card PeerAdmin#hlfv1 -A admin -S adminpw --file networkadmin.card
Starting business network property-network at version 0.2.6-deploy.113
Processing these Network Admins:
userName: admin
✖ Starting business network definition. This may take a minute...
Error: Error trying to start business network. Error: No valid responses from any peers.
Response from attempted peer comms was an error: Error: failed to execute transaction ae276da81f756ac76edccf85a79f1c11a554f1285c2a8c4cc2899db433220500: error starting container: error starting container: Failed to generate platform-specific docker build: Error returned from build: 1 "npm WARN notice [SECURITY] hoek has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=hoek&version=2.16.3 - Run npm i npm#latest -g to upgrade your npm version, and then npm audit to get more info.
npm WARN deprecated boom#2.10.1: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated cryptiles#2.0.5: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated hoek#2.16.3: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated boom#4.3.1: This version is no longer maintained. Please upgrade to the latest version.
x509#0.3.3 install /chaincode/output/node_modules/x509
node-gyp rebuild
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at PythonFinder.failNoPython (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:483:19)
gyp ERR! stack at PythonFinder. (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:397:16)
gyp ERR! stack at F (/usr/local/lib/node_modules/npm/node_modules/which/which.js:68:16)
gyp ERR! stack at E (/usr/local/lib/node_modules/npm/node_modules/which/which.js:80:29)
gyp ERR! stack at /usr/local/lib/node_modules/npm/node_modules/which/which.js:89:16
gyp ERR! stack at /usr/local/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5
gyp ERR! stack at /usr/local/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21)
gyp ERR! System Linux 4.10.0-28-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /chaincode/output/node_modules/x509
gyp ERR! node -v v8.4.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN The package composer-common is included as both a dev and production dependency.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! x509#0.3.3 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the x509#0.3.3 install 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! /root/.npm/_logs/2018-12-19T06_43_46_434Z-debug.log
"
Command failed
FABRIC_VERSION=hlfv12
COMPOSER_VERSION=v0.20.5
NODE_VERSION=v8.14.1
NPM_VERSION=6.4.1
I already done ./teardownfabric and ./stopFabric and again started a fabric and create a peeradmin card .
This is most likely caused by an old or incorrect image used to build chaincode images. As long as you haven't reconfigured your peer to use a different build image then the easiest fix for this is to delete any ccenv images you might have for example you could try
docker rmi $(docker images hyperledger/fabric-ccenv* -q) -f
to force remove all ccenv images
I installed the pod apollo according to this manual, then at the stage where you have to create a run-time, the build does not work, it returns this error I do not understand why ..
Can't find Apollo CLI. Installing...
npm ERR! Error while executing:
npm ERR! /Applications/Xcode.app/Contents/Developer/usr/bin/git ls-remote -h -t ssh://git#github.com/Project/fitto-ios.git
npm ERR!
npm ERR! git#github.com: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/mickaelbelhassen/.npm/_logs/2018-08-21T13_43_18_743Z-debug.log
Command /bin/sh failed with exit code 1
And I do not understand why he talks about git ..
Also, the repository ssh://git#github.com/Project/fitto-ios.git is my remote repository, it has nothing to do with Apollo.
Here is my run script is the same as the official documentation:
APOLLO_FRAMEWORK_PATH="$(eval find $FRAMEWORK_SEARCH_PATHS -name "Apollo.framework" -maxdepth 1)"
if [ -z "$APOLLO_FRAMEWORK_PATH" ]; then
echo "error: Couldn't find Apollo.framework in FRAMEWORK_SEARCH_PATHS; make sure to add the framework to your project."
exit 1
fi
cd "${SRCROOT}/${TARGET_NAME}"
$APOLLO_FRAMEWORK_PATH/check-and-run-apollo-cli.sh codegen:generate --queries="$(find . -name '*.graphql')" --schema=schema.json API.swift
You need to install the Apollo CLI from Here Then try building your app again.
I have followed the following tut:
https://docs.nativescript.org/tutorial/chapter-1#11-creating-apps
to create the demo app hello world, only when Im trying to run the last command in the cli:
npm run build-ios-bundle -- --release --copy-to HalloWorld.ipa
Builds the project for iOS and produces an APP or IPA that you can manually deploy in the iOS Simulator or on device, respectively.
IMPORTANT: Before building for iOS device, verify that you have configured a valid pair of certificate and provisioning profile on your OS X system.
Options
child process exited with code 127
npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/Cellar/node/7.9.0/bin/node" "/usr/local/bin/npm" "run" "ns-bundle" "--ios" "--build-app" "--release" "--copy-to" "HalloWorld.ipa"
npm ERR! node v7.9.0
npm ERR! npm v4.2.0
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! # ns-bundle: ns-bundle "HalloWorld.ipa"
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the # ns-bundle script 'ns-bundle "HalloWorld.ipa"'.
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! ns-bundle "HalloWorld.ipa"
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 ERR! Please include the following file with any support request:
npm ERR! /Users/Hugo/.npm/_logs/2017-04-12T14_47_59_306Z-debug.log
npm ERR! Darwin 16.0.0
npm ERR! argv "/usr/local/Cellar/node/7.9.0/bin/node" "/usr/local/bin/npm" "run" "build-ios-bundle" "--" "--release" "--copy-to" "HalloWorld.ipa"
npm ERR! node v7.9.0
npm ERR! npm v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! # build-ios-bundle: npm run ns-bundle --ios --build-app "--release" "--copy-to" "HalloWorld.ipa"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # build-ios-bundle script 'npm run ns-bundle --ios --build-app "--release" "--copy-to" "HalloWorld.ipa"'.
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 ns-bundle --ios --build-app "--release" "--copy-to" "HalloWorld.ipa"
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 ERR! Please include the following file with any support request:
npm ERR! /Users/Hugo/.npm/_logs/2017-04-12T14_47_59_349Z-debug.log
Debug log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node/7.9.0/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'run',
1 verbose cli 'build-ios-bundle',
1 verbose cli '--',
1 verbose cli '--release',
1 verbose cli '--copy-to',
1 verbose cli 'HalloWorld.ipa' ]
2 info using npm#4.2.0
3 info using node#v7.9.0
4 verbose run-script [ 'prebuild-ios-bundle',
4 verbose run-script 'build-ios-bundle',
4 verbose run-script 'postbuild-ios-bundle' ]
5 info lifecycle #~prebuild-ios-bundle: #
6 silly lifecycle #~prebuild-ios-bundle: no script for prebuild-ios-bundle, continuing
7 info lifecycle #~build-ios-bundle: #
8 verbose lifecycle #~build-ios-bundle: unsafe-perm in lifecycle true
9 verbose lifecycle #~build-ios-bundle: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/Hugo/Desktop/HelloWorld/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
10 verbose lifecycle #~build-ios-bundle: CWD: /Users/Hugo/Desktop/HelloWorld
11 silly lifecycle #~build-ios-bundle: Args: [ '-c',
11 silly lifecycle 'npm run ns-bundle --ios --build-app "--release" "--copy-to" "HalloWorld.ipa"' ]
12 silly lifecycle #~build-ios-bundle: Returned: code: 1 signal: null
13 info lifecycle #~build-ios-bundle: Failed to exec build-ios-bundle script
14 verbose stack Error: # build-ios-bundle: `npm run ns-bundle --ios --build-app "--release" "--copy-to" "HalloWorld.ipa"`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:194:7)
14 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:194:7)
14 verbose stack at maybeClose (internal/child_process.js:899:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid #
16 verbose cwd /Users/Hugo/Desktop/HelloWorld
17 error Darwin 16.0.0
18 error argv "/usr/local/Cellar/node/7.9.0/bin/node" "/usr/local/bin/npm" "run" "build-ios-bundle" "--" "--release" "--copy-to" "HalloWorld.ipa"
19 error node v7.9.0
20 error npm v4.2.0
21 error code ELIFECYCLE
22 error errno 1
23 error # build-ios-bundle: `npm run ns-bundle --ios --build-app "--release" "--copy-to" "HalloWorld.ipa"`
23 error Exit status 1
24 error Failed at the # build-ios-bundle script 'npm run ns-bundle --ios --build-app "--release" "--copy-to" "HalloWorld.ipa"'.
24 error Make sure you have the latest version of node.js and npm installed.
24 error If you do, this is most likely a problem with the package,
24 error not with npm itself.
24 error Tell the author that this fails on your system:
24 error npm run ns-bundle --ios --build-app "--release" "--copy-to" "HalloWorld.ipa"
24 error You can get information on how to open an issue for this project with:
24 error npm bugs
24 error Or if that isn't available, you can get their info via:
24 error npm owner ls
24 error There is likely additional logging output above.
25 verbose exit [ 1, true ]
Can you please help me,
Regards,
I just had the same issue, switching back to node 6.11 works fine.
Has anyone here got "electron" to work under tails distribution? Or any other download binary for that matter? I tried downloading the x64 binary
from the official site, but it won't execute it:
amnesia#amnesia:~/Desktop/temp$ ./electron --help
bash: ./electron: No such file or directory
I tried putting "bash" in front of it and I get a similar error:
amnesia#amnesia:~/Desktop/temp$ bash ./electron --help
./electron: ./electron: cannot execute binary file
I then installed npm and tried to install it from there and I'm getting the following error:
electron#1.6.6 postinstall /usr/local/lib/node_modules/electron
node install.js
sh: 1: node: Permission denied
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR! electron#1.6.6 postinstall: `node install.js`
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the electron#1.6.6 postinstall script.
npm ERR! This is most likely a problem with the electron package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls electron
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 4.8.0-0.bpo.2-amd64
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "electron"
npm ERR! cwd /home/amnesia/Desktop/prog
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/amnesia/Desktop/prog/npm-debug.log
npm ERR! not ok code 0
amnesia#amnesia:~/Desktop/prog$
Does tails somehow prevent downloaded binaries from executing? Are
there certain directories that don't allow executables? I am confused.
I am using tails 2.11
I was able to get electron to work in tails by downloading the "ia32" version of the binary. For some reason the electron x64 binary does not work, even though I am using the 64-bit version of tails.