npm@8.19.2 ppc64：來自 package.json 的腳本以“: --: not found”退出
[英]npm@8.19.2 ppc64: Scripts from package.json exit with ": --: not found"
問題描述
當運行 package.json 中聲明的任何腳本時，npm@8.19.2 (ppc64) 會退出而不引發 STDERR 消息，但不會執行腳本。 與npm@6.14.16在同一台機器上，腳本正常執行。 無論腳本是什么，顯示的消息都是<ScriptContent>: --: not found
這是導致此行為的 package.json 的示例：
{
"scripts": {
"npmversion": "npm -v"
}
}
通過 cli 調用腳本
npm run npmversion
結果如下 output
patrick@testas:~/example-issue-npm8$ npm run npmversion
> npmversion
> npm -v
npm -v: --: not found
這就是我得到的所有錯誤消息
環境：
- npm：8.19.2
- Node.js：v16.18.1
- 操作系統名稱：OS400 / IBM i v7r4m0
- 系統 Model 名稱：IBM i
大約一周前，我在這里為同樣的問題尋求幫助： https://github.com/npm/cli/issues/5904
使用--verbose運行腳本會導致以下 output
patrick@testas:~/example-issue-npm8$ npm run npmversion --verbose
npm verb cli /QOpenSys/pkgs/lib/nodejs16/bin/node /HODB/IFS/home/PATRICK/overrides/npm
npm info using npm@8.19.2
npm info using node@v16.18.1
npm timing npm:load:whichnode Completed in 1ms
npm timing config:load:defaults Completed in 3ms
npm timing config:load:file:/QOpenSys/pkgs/lib/nodejs16/lib/node_modules/npm/npmrc Completed in 2ms
npm timing config:load:builtin Completed in 2ms
npm timing config:load:cli Completed in 4ms
npm timing config:load:env Completed in 1ms
npm timing config:load:file:/HODB/IFS/home/PATRICK/example-issue-npm8/.npmrc Completed in 0ms
npm timing config:load:project Completed in 2ms
npm timing config:load:file:/HODB/IFS/home/PATRICK/.npmrc Completed in 2ms
npm timing config:load:user Completed in 2ms
npm timing config:load:file:/QOpenSys/pkgs/lib/nodejs16/etc/npmrc Completed in 0ms
npm timing config:load:global Completed in 0ms
npm timing config:load:validate Completed in 2ms
npm timing config:load:credentials Completed in 1ms
npm timing config:load:setEnvs Completed in 2ms
npm timing config:load Completed in 19ms
npm timing npm:load:configload Completed in 19ms
npm timing npm:load:mkdirpcache Completed in 2ms
npm timing npm:load:mkdirplogs Completed in 0ms
npm verb title npm run npmversion
npm verb argv "run" "npmversion" "--loglevel" "verbose"
npm timing npm:load:setTitle Completed in 2ms
npm timing config:load:flatten Completed in 5ms
npm timing npm:load:display Completed in 14ms
npm verb logfile logs-max:10 dir:/HODB/IFS/home/PATRICK/.npm/_logs
npm verb logfile /HODB/IFS/home/PATRICK/.npm/_logs/2022-12-07T08_17_22_935Z-debug-0.log
npm timing npm:load:logFile Completed in 14ms
npm timing npm:load:timers Completed in 0ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load Completed in 53ms
> npmversion
> npm -v
npm -v: --: not found
npm timing command:run Completed in 108ms
npm verb exit 127
npm timing npm Completed in 181ms
npm verb code 127
為了進行比較，這里是使用 npm@6.14.16 執行的相同腳本，它在我們的系統上仍然可用。 在這種情況下，腳本會按預期執行。
patrick@testas:~/example-issue-npm8$ npm run npmversion --verbose
npm info it worked if it ends with ok
npm verb cli [
npm verb cli '/QOpenSys/pkgs/lib/nodejs12/bin/node',
npm verb cli '/QOpenSys/pkgs/bin/npm',
npm verb cli 'run',
npm verb cli 'npmversion',
npm verb cli '--verbose'
npm verb cli ]
npm info using npm@6.14.16
npm info using node@v12.22.11
npm verb run-script [ 'prenpmversion', 'npmversion', 'postnpmversion' ]
npm info lifecycle @~prenpmversion: @
npm info lifecycle @~npmversion: @
> @ npmversion /HODB/IFS/home/PATRICK/example-issue-npm8
> npm -v
6.14.16
npm verb lifecycle @~npmversion: unsafe-perm in lifecycle true
npm verb lifecycle @~npmversion: PATH: /QOpenSys/pkgs/lib/nodejs12/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/HODB/IFS/home/PATRICK/example-issue-npm8/node_modules/.bin:/QOpenSys/pkgs/bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
npm verb lifecycle @~npmversion: CWD: /HODB/IFS/home/PATRICK/example-issue-npm8
npm info lifecycle @~postnpmversion: @
npm verb exit [ 0, true ]
npm timing npm Completed in 2255ms
npm info ok
我第一次意識到這種行為是在通過 yum 更新各種開源運行時包之后。 許多軟件包已更新，因此很難找出哪一個可能導致問題。 如有必要，我將研究獲取有關之前和現在安裝的 package 版本的詳細信息。
在批量更新之前，我手動從nodejs16.ppc64 16.18.1-1 @ibmi-base拉取更新
當只有這個 package 被更新時，運行時表現如常。 大約在批量更新一周后，我偶然遇到了這個問題。 我們計划盡快從 nodejs12 更新到 nodejs16，因此 nodejs16 目前沒有正常使用。
由於 npm 使用 python，我嘗試使用不同pyhton/python2/python3版本並提供--python=<PythonPackage>參數，但沒有成功。
package.json 的錯誤已通過創建一個新的空目錄排除，該目錄包含上面提供的剝離的 package.json。
通過對另一個用戶配置文件進行相同的嘗試，排除了我的用戶配置存在的問題。 另一個用戶配置文件用於批處理執行，因此用戶的配置非常平淡。
到目前為止，無論我嘗試過什么，npm@8 都會顯示相同的 - 錯誤的 - 行為。
這是關於當前安裝在我們機器上的 yum 包的完整聲明
patrick@testas:~/example-issue-npm8$ yum list installed
http://weitswtools.ad.holter.at/YUMRepos/openmax/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
Installed Packages
autoconf.noarch 2.69-3 @ibm/7.3
automake.noarch 1.15-3 @ibm/7.3
bash.ppc64 5.1-3 @ibmi-base
bzip2.ppc64 1.0.6-16 @ibmi-base
ca-certificates.noarch 2_git20170807.10b2785-6 @ibmi-base
ca-certificates-mozilla.noarch 2022.2.58-1 @ibmi-base
charset-alias.ppc64 1.14-6 @ibmi-base
cmake.ppc64 3.16.9-1 @ibm
coreutils-gnu.ppc64 8.25-9 @ibmi-base
coreutils-pase-dummy.ppc 7.3-1 @ibmi-base
cpio-gnu.ppc64 2.12-2 @ibmi-base
createrepo.noarch 0.10.4-4 @ibm/7.3
curl.ppc64 7.76.1-2 @ibmi-base
db.ppc64 4.8.30-3 @ibm/7.3
db2util.ppc64 1.0.12-1 @ibm
dos2unix.ppc64 7.4.1-1 @ibm/7.3
file-magic.ppc64 5.32-7 @ibmi-base
filesystem-dummy.noarch 7.3-1 @ibmi-base
findutils.ppc64 4.6.0-5 @ibmi-base
fribidi.ppc64 1.0.5-1 @openmax/7.3
gcc6-aix.fat 6.3.0-29 @ibm/7.3
gcc6-cplusplus-aix.fat 6.3.0-29 @ibm/7.3
gcc6-cpp-aix.fat 6.3.0-29 @ibm/7.3
gettext-runtime.ppc64 0.19.8-2 @ibmi-base
gettext-tools.ppc64 0.19.8-2 @ibmi-base
git.ppc64 2.26.2-3 @ibm/7.3
glib2.ppc64 2.52.0-5 @ibmi-base
gmp-aix.fat 5.1.3-14 @ibm/7.3
grep-gnu.ppc64 3.0-3 @ibmi-base
gzip.ppc64 1.8-4 @ibmi-base
ibmi-repos.noarch 7.3-3 @ibmi-release
iconv-gnu.ppc64 1.14-6 @ibmi-base
inetutils-ping.ppc64 1.9.4-0 @openmax/7.3
jq.ppc64 1.6-2 @ibm/7.3
less.ppc64 551-1 @ibm/7.3
lftp.ppc64 4.9.2-1 @ibmi-base
libICE6.ppc64 1.0.10-3 @ibm/7.3
libSM6.ppc64 1.2.3-3 @ibm/7.3
libX11-data.noarch 1.7.0-3 @ibm/7.3
libX11-xcb1.ppc64 1.7.0-3 @ibm/7.3
libXau6.ppc64 1.0.9-4 @ibm/7.3
libXdmcp6.ppc64 1.1.3-4 @ibm/7.3
libarchive13.ppc64 3.3.3-2 @ibmi-base
libatomic1.ppc64 10.3.0-11 @ibmi-base
libblas3.ppc64 3.8.0-2 @ibm/7.3
libbrotlicommon1.ppc64 1.0.9-2 @ibmi-base
libbrotlidec1.ppc64 1.0.9-2 @ibmi-base
libbz2-1.ppc64 1.0.6-16 @ibmi-base
libcurl4.ppc64 7.76.1-2 @ibmi-base
libdb48.ppc64 4.8.30-3 @ibm/7.3
libedit0.ppc64 3.1.snap20180525-0 @openmax/7.3
libexpat1.ppc64 2.2.9-2 @ibmi-base
libffi6.ppc64 3.2.1-3 @ibmi-base
libfontconfig1.ppc64 2.13.92-1 @ibm/7.3
libfreetype6.ppc64 2.10.4-1 @ibm/7.3
libgcc-aix.fat 6.3.0-29 @ibm/7.3
libgcc_s1.ppc64 10.3.0-11 @ibmi-base
libgfortran3.ppc64 6.3.0-29 @ibm/7.3
libgio-2_0-0.ppc64 2.52.0-5 @ibmi-base
libglib-2_0-0.ppc64 2.52.0-5 @ibmi-base
libgmodule-2_0-0.ppc64 2.52.0-5 @ibmi-base
libgobject-2_0-0.ppc64 2.52.0-5 @ibmi-base
libgomp1.ppc64 10.3.0-11 @ibmi-base
libiconv2.ppc64 1.14-6 @ibmi-base
libicu69.ppc64 69.1-1 @ibm/7.3
libidn2-0.ppc64 2.3.0-4 @ibmi-base
libintl9.ppc64 0.19.8-2 @ibmi-base
libjpeg8.ppc64 1.5.1-2 @ibm/7.3
libjq1.ppc64 1.6-2 @ibm/7.3
liblapack3.ppc64 3.8.0-2 @ibm/7.3
liblua5_3.ppc64 5.3.4-4 @ibmi-base
liblzma5.ppc64 5.2.3-5 @ibmi-base
liblzo2.ppc64 2.10-1 @ibm/7.3
libmagic1.ppc64 5.32-7 @ibmi-base
libmpc-aix.fat 1.0.3-15 @ibm/7.3
libncurses6.ppc64 6.0-9 @ibmi-base
libodbc2.ppc64 2.3.9-1 @ibm/7.3
libonig5.ppc64 6.9.4-1 @ibm/7.3
libopenssl1_1.ppc64 1.1.1q-1 @ibmi-base
libp11-kit0.ppc64 0.23.14-4 @ibmi-base
libpcre1.ppc64 8.45-2 @ibmi-base
libpcre2-8-0.ppc64 10.35-1 @ibm/7.3
libpng16.ppc64 1.6.37-0 @ibm/7.3
libpopt0.ppc64 1.16-3 @ibmi-base
libreadline6.ppc64 6.3-5 @ibm/7.3
libreadline8.ppc64 8.1-3 @ibmi-base
libslang2.ppc64 2.3.1a-4 @ibm/7.3
libsqlite3-0.ppc64 3.32.3-2 @ibmi-base
libssh2-1.ppc64 1.9.0-4 @ibmi-base
libstdcplusplus-aix.fat 6.3.0-29 @ibm/7.3
libstdcplusplus6.ppc64 10.3.0-11 @ibmi-base
libtasn1-6.ppc64 4.10-5 @ibmi-base
libtiff5.ppc64 4.0.9-0 @ibm/7.3
libtool.ppc64 2.4.6-5 @ibm/7.3
libutil2.ppc64 0.12.0-2 @ibmi-base
libuuid1.ppc64 2.35.1-3 @ibm/7.3
libuv1.ppc64 1.42.0-1 @ibm
libxml2-2.ppc64 2.9.4-6 @ibmi-base
libz1.ppc64 1.2.13-1 @ibmi-base
libzstd1.ppc64 1.5.2-1 @ibm
m4-gnu.ppc64 1.4.17-2 @ibmi-base
make-gnu.ppc64 4.2-3 @ibmi-base
maven.noarch 3.6.0-2 @ibm
mpfr-aix.fat 3.1.2-13 @ibm/7.3
nano.ppc64 5.3-1 @ibm/7.3
ncurses-terminfo.ppc64 6.0-9 @ibmi-base
nodejs12.ppc64 12.22.11-1 @ibm
nodejs16.ppc64 16.18.1-1 @ibmi-base
nodever.noarch 1.0.0-4 @ibm/7.3
nspr.ppc64 4.32-1 @ibm
nss.ppc64 3.68.1-1 @ibm
openssh.ppc64 8.1p1-1 @ibm
openssl-devel.ppc64 1.1.1q-1 @ibmi-base
p11-kit.ppc64 0.23.14-4 @ibmi-base
p11-kit-trust.ppc64 0.23.14-4 @ibmi-base
p7zip.ppc64 16.02-2 @ibm/7.3
pase-libs-dummy.fat 7.3-1 @ibmi-base
patch-gnu.ppc64 2.7.5-5 @ibmi-base
perl.ppc64 5.24.1-5 @ibmi-base
pkg-config.ppc64 0.29.2-2 @ibm/7.3
python2.ppc64 2.7.18-6 @ibm
python2-deltarpm.ppc64 3.6.1-3 @ibm/7.3
python2-devel.ppc64 2.7.18-6 @ibm
python2-iniparse.noarch 0.4-2 @ibm/7.3
python2-pip.noarch 9.0.1-3 @ibm/7.3
python2-pycurl.ppc64 7.43.0-4 @ibm/7.3
python2-rpm.ppc64 4.13.1-15 @ibmi-base
python2-setuptools.noarch 36.0.1-3 @ibm/7.3
python2-urlgrabber.noarch 3.10.2-3 @ibm/7.3
python2-wheel.noarch 0.29.0-3 @ibm/7.3
python3.ppc64 3.6.15-1 @ibm
python3-pip.noarch 21.1.2-1 @ibm
python3-setuptools.noarch 57.0.0-1 @ibm
python3-wheel.noarch 0.36.2-1 @ibm
rpm.ppc64 4.13.1-15 @ibmi-base
rpm-build.ppc64 4.13.1-15 @ibmi-base
rpm-devel.ppc64 4.13.1-15 @ibmi-base
rpmdevtools.noarch 8.10-2 @ibm/7.3
rsync.ppc64 3.2.3-3 @ibm
sed-gnu.ppc64 4.4-2 @ibmi-base
tar-gnu.ppc64 1.29-6 @ibmi-base
unixODBC.ppc64 2.3.9-1 @ibm/7.3
unzip.ppc64 6.0-4 @ibmi-base
update-alternatives.ppc64 1.19.7-2 @ibmi-base
vim.ppc64 8.1-3 @ibm/7.3
wget.ppc64 1.20.3-3 @ibm/7.3
yum.noarch 3.4.3-22 @ibmi-base
yum-metadata-parser.ppc64 1.1.4-3 @ibmi-base
yum-plugin-fastestmirror.noarch 1.1.31-9 @ibmi-base
yum-plugin-local.noarch 1.1.31-9 @ibmi-base
yum-utils.noarch 1.1.31-9 @ibmi-base
zip.ppc64 3.0-4 @ibmi-base
patrick@testas:~/example-issue-npm8$
1 個解決方案
解決方案1
0 2023-01-19 11:01:33
我不知道問題出在哪里，但是在為 nodejs16.ppc64 安裝另一個更新后問題就消失了。
如何在 package.json (NodeJS) 中使用 npm 腳本添加參數
[英]How to add paramater with npm scripts in package.json (NodeJS)
在Windows上的package.json中外部定位的'npm run'腳本？
[英]Externally-located 'npm run' scripts in package.json on Windows?
聲明:本站的技術帖子網頁，遵循CC BY-SA 4.0協議，如果您需要轉載，請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.
相關問題
NPM 在 linux PPC64 上安裝返回分段錯誤
沒有調用npm package.json腳本
npm package.json 中沒有運行腳本
使用npm和yarn的package.json腳本？
覆蓋 package.json 腳本 - NPM
npm package.json 腳本的參數化
在 package.json 腳本鍵：npm 運行與否？
從package.json運行兩個腳本
如何在 package.json (NodeJS) 中使用 npm 腳本添加參數
在Windows上的package.json中外部定位的'npm run'腳本？
相關標簽