加入收藏 | 设为首页 | 会员中心 | 我要投稿 李大同 (https://www.lidatong.com.cn/)- 科技、建站、经验、云计算、5G、大数据,站长网!
当前位置: 首页 > 综合聚焦 > 服务器 > 安全 > 正文

azure – npm ERR! 404未找到:har-validator@5.1.2

发布时间:2020-12-17 17:57:35 所属栏目:安全 来源:网络整理
导读:升级到angular7后,“npm install”步骤中的azure构建失败. 在当地一切正常. 我试过了: 将构建定义中的clean选项设置为true,并设置为“all directories”. 在安装步骤之前强制执行npm更新“npm @ latest -g”步骤 将Portal中应用程序设置中的“WEBSITE_NODE_
升级到angular7后,“npm install”步骤中的azure构建失败.
在当地一切正常.

我试过了:

>将构建定义中的clean选项设置为true,并设置为“all directories”.
>在安装步骤之前强制执行npm更新“npm @ latest -g”步骤
>将Portal中应用程序设置中的“WEBSITE_NODE_DEFAULT_VERSION”设置为与本地版本相同的版本(10.14.1).

但我仍然从“npm install”步骤获得以下错误输出.
(请注意,代理程序未使用与默认值设置相同的版本)

我的最后一个选项(我认为)是删除整个服务并创建一个具有相同名称的新服务 – 但我想避免这样做..

关于输出中的最后一个错误(npm ERR!404 Not Found:har-validator@5.1.2),我不知道这是什么,但它不包含在我的package.json中.我相信它可能是cli包正在使用的东西?

2018-12-11T21:46:07.1672265Z ##[section]Starting: npm install
2018-12-11T21:46:07.1675810Z ==============================================================================
2018-12-11T21:46:07.1675868Z Task         : npm
2018-12-11T21:46:07.1675929Z Description  : Run an npm command
2018-12-11T21:46:07.1675961Z Version      : 0.2.27
2018-12-11T21:46:07.1675996Z Author       : Microsoft Corporation
2018-12-11T21:46:07.1676309Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkID=613746)
2018-12-11T21:46:07.1676342Z ==============================================================================
2018-12-11T21:46:07.7212998Z [command]C:Windowssystem32cmd.exe /D /S /C ""C:Program Filesnodejsnpm.cmd" config list"
2018-12-11T21:46:25.4985558Z ; cli configs
2018-12-11T21:46:25.4985985Z metrics-registry = "https://registry.npmjs.org/"
2018-12-11T21:46:25.4986124Z scope = ""
2018-12-11T21:46:25.4986277Z user-agent = "npm/6.4.1 node/v10.13.0 win32 x64"
2018-12-11T21:46:25.4986429Z 
2018-12-11T21:46:25.4986565Z ; environment configs
2018-12-11T21:46:25.4986753Z cache = "C:npmcache"
2018-12-11T21:46:25.4986863Z prefix = "C:npmprefix"
2018-12-11T21:46:25.4986958Z 
2018-12-11T21:46:25.4987093Z ; builtin config undefined
2018-12-11T21:46:25.4987188Z 
2018-12-11T21:46:25.4987354Z ; node bin location = C:Program Filesnodejsnode.exe
2018-12-11T21:46:25.4987583Z ; cwd = D:a1ssrcFightplan_v1
2018-12-11T21:46:25.4987728Z ; HOME = C:UsersVssAdministrator
2018-12-11T21:46:25.4987911Z ; "npm config ls -l" to show all defaults.
2018-12-11T21:46:25.4988084Z 
2018-12-11T21:46:25.5112108Z [command]C:Windowssystem32cmd.exe /D /S /C ""C:Program Filesnodejsnpm.cmd" install"
2018-12-11T21:47:30.4103336Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staginguglify-es-2690efe8package.json'
2018-12-11T21:47:30.5364487Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staginguglify-es-2690efe8LICENSE'
2018-12-11T21:47:30.6517880Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staginguglify-es-2690efe8README.md'
2018-12-11T21:47:30.8043664Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingajv-dc7fc88alib.DS_Store'
2018-12-11T21:47:31.0212461Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingwebpack-subresource-integrity-6d084f0dexampleswebpack4-contenthash-issue-83README.md'
2018-12-11T21:47:31.0214504Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingajv-dc7fc88alibajv.d.ts'
2018-12-11T21:47:31.1252776Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingwebpack-subresource-integrity-6d084f0dexampleswebpack4-contenthash-issue-83index.js'
2018-12-11T21:47:31.1989574Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingajv-dc7fc88alibajv.js'
2018-12-11T21:47:31.3153484Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingwebpack-subresource-integrity-6d084f0dexamplesmini-css-extract-plugindistindex.js'
2018-12-11T21:47:31.4413192Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingajv-dc7fc88alibcache.js'
2018-12-11T21:47:31.4418678Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingmoment-b4a9e1a1srclibparseregex.js'
2018-12-11T21:47:31.6315506Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingnode-gyp-6d42b3ccgyptoolsXcodeSpecificationsgyp.pbfilespec'
2018-12-11T21:47:31.6315920Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingmoment-b4a9e1a1srclibparsetoken.js'
2018-12-11T21:47:31.6432211Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingbody-parser-5b44689clibtypesjson.js'
2018-12-11T21:47:31.6516115Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingnode-gyp-6d42b3ccgyptoolsXcodeSpecificationsgyp.xclangspec'
2018-12-11T21:47:31.6572566Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingunique-filename-a895a9aecoverage__root__index.html'
2018-12-11T21:47:31.6605443Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingjson-schema-traverse-23dbd864specfixturesschema.js'
2018-12-11T21:47:31.7477508Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingunique-filename-a895a9aecoverage__root__index.js.html'
2018-12-11T21:47:31.7575572Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingbody-parser-5b44689clibtypesraw.js'
2018-12-11T21:47:31.7740463Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staging@angularcompiler-cli-3421191esrcngtschostsrcreflection.d.ts'
2018-12-11T21:47:31.7761304Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingjson-schema-traverse-23dbd864specindex.spec.js'
2018-12-11T21:47:31.7898919Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingbody-parser-5b44689clibtypestext.js'
2018-12-11T21:47:31.8368271Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staging@angularcompiler-cli-3421191esrcngtschostsrcreflection.js'
2018-12-11T21:47:31.8425215Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingbody-parser-5b44689clibtypesurlencoded.js'
2018-12-11T21:47:31.9064194Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingprimeng-e2ced65bcomponentsdatalistdatalist.d.ts'
2018-12-11T21:47:31.9116674Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingprimeng-e2ced65bcomponentsdatalistdatalist.js'
2018-12-11T21:47:31.9175038Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingprimeng-e2ced65bcomponentsdatalistdatalist.js.map'
2018-12-11T21:47:31.9218406Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingprimeng-e2ced65bcomponentsdatalistdatalist.metadata.json'
2018-12-11T21:47:32.0569111Z npm WARN tar ENOENT: no such file or directory,lstat 'D:a1ssrcFightplan_v1node_modules.stagingprimeng-e2ced65bcomponents'
2018-12-11T21:47:32.6149587Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingnode-sass-e876628dsrclibsasssrcutf8checked.h'
2018-12-11T21:47:33.6779419Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingprimeng-e2ced65bcomponentsgmapgmap.d.ts'
2018-12-11T21:47:33.6899685Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingprimeng-e2ced65bcomponentsgmapgmap.js'
2018-12-11T21:47:33.7021864Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingprimeng-e2ced65bcomponentsgmapgmap.js.map'
2018-12-11T21:47:33.7105126Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingprimeng-e2ced65bcomponentsgmapgmap.metadata.json'
2018-12-11T21:47:33.7420473Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staging@angularcommon-66e6ce23esm5srcpipesdeprecateddate_pipe.js'
2018-12-11T21:47:33.7477117Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staging@angular-devkitschematics-b141a7e4taskstslint-fixtestrulescustomRuleRule.js'
2018-12-11T21:47:33.7574105Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staging@angularcommon-66e6ce23esm5srcpipesdeprecatedindex.js'
2018-12-11T21:47:33.7578418Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staging@angular-devkitschematics-b141a7e4taskstslint-fixtestrun-task.d.ts'
2018-12-11T21:47:33.7583385Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staging@angularcommon-66e6ce23esm5srcpipesdeprecatedintl.js'
2018-12-11T21:47:33.7583560Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staging@angular-devkitschematics-b141a7e4taskstslint-fixtestrun-task.js'
2018-12-11T21:47:33.7763116Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingtslint-63def258libverifylines.d.ts'
2018-12-11T21:47:33.7764349Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingtslint-63def258libverifylines.js'
2018-12-11T21:47:33.8244897Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingnode-sass-f11b263ctestfixturesinput-directorysassnestedthree.scss'
2018-12-11T21:47:33.8255514Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingnode-sass-f11b263ctestfixturesinput-directorysassone.scss'
2018-12-11T21:47:33.8283952Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingnode-sass-f11b263ctestfixturesinput-directorysasstwo.scss'
2018-12-11T21:47:33.8300811Z npm WARN tar ENOENT: no such file or directory,lstat 'D:a1ssrcFightplan_v1node_modules.stagingnode-sass-f11b263ctestfixtures'
2018-12-11T21:47:33.9502082Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.staging@schematicsangular-5e588af5universalfilessrc__main@stripTsExtension__.ts'
2018-12-11T21:47:34.9391213Z npm WARN tar ENOENT: no such file or directory,lstat 'D:a1ssrcFightplan_v1node_modules.staging@schematicsangular-5e588af5universalfilessrc'
2018-12-11T21:47:34.9391576Z npm WARN tar ENOENT: no such file or directory,lstat 'D:a1ssrcFightplan_v1node_modules.staging@angularcore-dcf43933esm5srcrender3interfaces'
2018-12-11T21:47:34.9393379Z npm WARN tar ENOENT: no such file or directory,open 'D:a1ssrcFightplan_v1node_modules.stagingprimeng-e2ced65bresourcescomponentstoasttoast.css'
2018-12-11T21:47:36.4859640Z npm WARN @ngrx/effects@6.1.2 requires a peer of @angular/core@^6.0.0 but none is installed. You must install peer dependencies yourself.
2018-12-11T21:47:36.4859826Z npm WARN @ngrx/entity@6.1.2 requires a peer of @angular/core@^6.0.0 but none is installed. You must install peer dependencies yourself.
2018-12-11T21:47:36.4859978Z npm WARN @ngrx/router-store@6.1.2 requires a peer of @angular/common@^6.0.0 but none is installed. You must install peer dependencies yourself.
2018-12-11T21:47:36.4860036Z npm WARN @ngrx/router-store@6.1.2 requires a peer of @angular/core@^6.0.0 but none is installed. You must install peer dependencies yourself.
2018-12-11T21:47:36.4860119Z npm WARN @ngrx/router-store@6.1.2 requires a peer of @angular/router@^6.0.0 but none is installed. You must install peer dependencies yourself.
2018-12-11T21:47:36.4860193Z npm WARN @ngrx/store@6.1.2 requires a peer of @angular/core@^6.0.0 but none is installed. You must install peer dependencies yourself.
2018-12-11T21:47:36.4860248Z npm WARN ajv-keywords@3.2.0 requires a peer of ajv@^6.0.0 but none is installed. You must install peer dependencies yourself.
2018-12-11T21:47:36.4860313Z npm WARN @1.0.0 No description
2018-12-11T21:47:36.4860359Z npm WARN @1.0.0 No repository field.
2018-12-11T21:47:36.4860411Z npm WARN The package jquery is included as both a dev and production dependency.
2018-12-11T21:47:36.4860686Z 
2018-12-11T21:47:36.4860757Z npm ERR! code E404
2018-12-11T21:47:36.4860803Z npm ERR! 404 Not Found: har-validator@5.1.2
2018-12-11T21:47:36.5420339Z 
2018-12-11T21:47:36.5421133Z npm ERR! A complete log of this run can be found in:
2018-12-11T21:47:36.5421305Z npm ERR!     C:npmcache_logs2018-12-11T21_47_36_496Z-debug.log
2018-12-11T21:47:36.6035543Z ##[error]npm failed with error: C:Program Filesnodejsnpm.cmd failed with return code: 1
2018-12-11T21:47:36.6062198Z ##[section]Finishing: npm install

解决方法

经过大量测试后,我发现应用程序中存在一个旧的package-lock.json.

删除package-lock.json并运行新的构建修复了问题..

(编辑:李大同)

【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容!

    推荐文章
      热点阅读