GVKun编程网logo

eslint npm 错误！ 404 未找到 - GET https://registry.npmjs.org/eslist - 未找到（未找到npm包入口文件）

5

对于想了解eslintnpm错误！404未找到-GEThttps://registry.npmjs.org/eslist-未找到的读者，本文将提供新的信息，我们将详细介绍未找到npm包入口文件，并且为

对于想了解eslint npm 错误！ 404 未找到 - GET https://registry.npmjs.org/eslist - 未找到的读者，本文将提供新的信息，我们将详细介绍未找到npm包入口文件，并且为您提供关于$ npm install eslint -g = -bash: $: 命令未找到、asp.net – 问题映射HttpHandler – > HTTP错误404未找到、azure – npm ERR！ 404未找到：har-validator@5.1.2、docker npm install错误：getaddrinfo ENOTFOUND注册表.npmjs.org注册表.npmjs.org：443的有价值信息。

本文目录一览：

eslint npm 错误！ 404 未找到 - GET https://registry.npmjs.org/eslist - 未找到（未找到npm包入口文件）

eslint npm 错误！ 404 未找到 - GET https://registry.npmjs.org/eslist - 未找到（未找到npm包入口文件）

愚蠢的错别字。我应该有类型 eslint 而不是 eslist

$ npm install eslint -g = -bash: $: 命令未找到

$ npm install eslint -g = -bash: $: 命令未找到

具体是什么没有“发现”？是 NPM 吗？如果是这样，请检查您的 PATH 变量。

由于您使用的是 Mac，它应该在这里：

/usr/local/bin/npm

另外，这是一个非常普遍和常见的问题，请在发布之前多做一些研究。

编辑：根据我下面的评论。

您是否在该命令的开头传递了 $:？在大多数文档中，这是指 shell 命令提示符，不应包含在命令中。

asp.net – 问题映射HttpHandler – > HTTP错误404未找到

asp.net – 问题映射HttpHandler – > HTTP错误404未找到

我有问题尝试映射HttpHandler在web.config中。

这是相关的配置位：

<httpHandlers>
  <add verb="*" path="*.hndlr" type="MyAssembly.MyHandler,MyAssembly" validate="false" />
</httpHandlers>

当我导航到http：//localhost/myApp/whatever.hndlr我得到服务器错误404(找不到)。

这是我第一次挂上HttpHandler，所以我可能会失去的东西 – 任何帮助赞赏！

更新：

我设法得到它工作使用两个答案到目前为止 – 谁能够exaplin为什么它的工作得到标记的答案！

这是我的配置(不会工作，如果没有两个 – 我在运行IIS7在经典模式)

System.web：

<httpHandlers>
    <add verb="*" path="*MyHandler.hndlr" type="MyAssembly.MyAssemblyHandler,MyAssembly" validate="false"/>
</httpHandlers>

System.webserver：

<handlers>
    <add name="MyHandler" verb="*" path="*MyHandler.hndlr" type="MyAssembly.MyAssemblyHandler,MyAssembly" validate="false" modules="IsapiModule" scriptprocessor="C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script"/>
</handlers>

解决方法

你使用IIS7，如果是这样的应用程序池运行在经典或流水线模式？如果它是IIS7在流水线模式，那么处理程序引用需要进入以下部分 
<system.webServer>
    <handlers>
    </handlers>
<system.webServer>

而不是在以下部分。

<system.web>
    <httpHandlers>
    </httpHandlers>
</system.web>

azure – npm ERR！ 404未找到：har-validator@5.1.2

azure – npm ERR！ 404未找到：har-validator@5.1.2

升级到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:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.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:\\npm\\cache"
2018-12-11T21:46:25.4986863Z prefix = "C:\\npm\\prefix"
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 Files\nodejs\node.exe
2018-12-11T21:46:25.4987583Z ; cwd = D:\a\1\s\src\fightplan_v1
2018-12-11T21:46:25.4987728Z ; HOME = C:\Users\VssAdministrator
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:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" install"
2018-12-11T21:47:30.4103336Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\uglify-es-2690efe8\package.json'
2018-12-11T21:47:30.5364487Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\uglify-es-2690efe8\LICENSE'
2018-12-11T21:47:30.6517880Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\uglify-es-2690efe8\README.md'
2018-12-11T21:47:30.8043664Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\ajv-dc7fc88a\lib\.DS_Store'
2018-12-11T21:47:31.0212461Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\webpack-subresource-integrity-6d084f0d\examples\webpack4-contenthash-issue-83\README.md'
2018-12-11T21:47:31.0214504Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\ajv-dc7fc88a\lib\ajv.d.ts'
2018-12-11T21:47:31.1252776Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\webpack-subresource-integrity-6d084f0d\examples\webpack4-contenthash-issue-83\index.js'
2018-12-11T21:47:31.1989574Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\ajv-dc7fc88a\lib\ajv.js'
2018-12-11T21:47:31.3153484Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\webpack-subresource-integrity-6d084f0d\examples\mini-css-extract-plugin\dist\index.js'
2018-12-11T21:47:31.4413192Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\ajv-dc7fc88a\lib\cache.js'
2018-12-11T21:47:31.4418678Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\moment-b4a9e1a1\src\lib\parse\regex.js'
2018-12-11T21:47:31.6315506Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\node-gyp-6d42b3cc\gyp\tools\Xcode\Specifications\gyp.pbfilespec'
2018-12-11T21:47:31.6315920Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\moment-b4a9e1a1\src\lib\parse\token.js'
2018-12-11T21:47:31.6432211Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\body-parser-5b44689c\lib\types\json.js'
2018-12-11T21:47:31.6516115Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\node-gyp-6d42b3cc\gyp\tools\Xcode\Specifications\gyp.xclangspec'
2018-12-11T21:47:31.6572566Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\unique-filename-a895a9ae\coverage\__root__\index.html'
2018-12-11T21:47:31.6605443Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\json-schema-traverse-23dbd864\spec\fixtures\schema.js'
2018-12-11T21:47:31.7477508Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\unique-filename-a895a9ae\coverage\__root__\index.js.html'
2018-12-11T21:47:31.7575572Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\body-parser-5b44689c\lib\types\raw.js'
2018-12-11T21:47:31.7740463Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@angular\compiler-cli-3421191e\src\ngtsc\host\src\reflection.d.ts'
2018-12-11T21:47:31.7761304Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\json-schema-traverse-23dbd864\spec\index.spec.js'
2018-12-11T21:47:31.7898919Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\body-parser-5b44689c\lib\types\text.js'
2018-12-11T21:47:31.8368271Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@angular\compiler-cli-3421191e\src\ngtsc\host\src\reflection.js'
2018-12-11T21:47:31.8425215Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\body-parser-5b44689c\lib\types\urlencoded.js'
2018-12-11T21:47:31.9064194Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\primeng-e2ced65b\components\datalist\datalist.d.ts'
2018-12-11T21:47:31.9116674Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\primeng-e2ced65b\components\datalist\datalist.js'
2018-12-11T21:47:31.9175038Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\primeng-e2ced65b\components\datalist\datalist.js.map'
2018-12-11T21:47:31.9218406Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\primeng-e2ced65b\components\datalist\datalist.Metadata.json'
2018-12-11T21:47:32.0569111Z npm WARN tar ENOENT: no such file or directory,lstat 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\primeng-e2ced65b\components'
2018-12-11T21:47:32.6149587Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\node-sass-e876628d\src\libsass\src\utf8\checked.h'
2018-12-11T21:47:33.6779419Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\primeng-e2ced65b\components\gmap\gmap.d.ts'
2018-12-11T21:47:33.6899685Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\primeng-e2ced65b\components\gmap\gmap.js'
2018-12-11T21:47:33.7021864Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\primeng-e2ced65b\components\gmap\gmap.js.map'
2018-12-11T21:47:33.7105126Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\primeng-e2ced65b\components\gmap\gmap.Metadata.json'
2018-12-11T21:47:33.7420473Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@angular\common-66e6ce23\esm5\src\pipes\deprecated\date_pipe.js'
2018-12-11T21:47:33.7477117Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@angular-devkit\schematics-b141a7e4\tasks\tslint-fix\test\rules\customruleRule.js'
2018-12-11T21:47:33.7574105Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@angular\common-66e6ce23\esm5\src\pipes\deprecated\index.js'
2018-12-11T21:47:33.7578418Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@angular-devkit\schematics-b141a7e4\tasks\tslint-fix\test\run-task.d.ts'
2018-12-11T21:47:33.7583385Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@angular\common-66e6ce23\esm5\src\pipes\deprecated\intl.js'
2018-12-11T21:47:33.7583560Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@angular-devkit\schematics-b141a7e4\tasks\tslint-fix\test\run-task.js'
2018-12-11T21:47:33.7763116Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\tslint-63def258\lib\verify\lines.d.ts'
2018-12-11T21:47:33.7764349Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\tslint-63def258\lib\verify\lines.js'
2018-12-11T21:47:33.8244897Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\node-sass-f11b263c\test\fixtures\input-directory\sass\nested\three.scss'
2018-12-11T21:47:33.8255514Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\node-sass-f11b263c\test\fixtures\input-directory\sass\one.scss'
2018-12-11T21:47:33.8283952Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\node-sass-f11b263c\test\fixtures\input-directory\sass\two.scss'
2018-12-11T21:47:33.8300811Z npm WARN tar ENOENT: no such file or directory,lstat 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\node-sass-f11b263c\test\fixtures'
2018-12-11T21:47:33.9502082Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@schematics\angular-5e588af5\universal\files\src\__main@stripTsExtension__.ts'
2018-12-11T21:47:34.9391213Z npm WARN tar ENOENT: no such file or directory,lstat 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@schematics\angular-5e588af5\universal\files\src'
2018-12-11T21:47:34.9391576Z npm WARN tar ENOENT: no such file or directory,lstat 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\@angular\core-dcf43933\esm5\src\render3\interfaces'
2018-12-11T21:47:34.9393379Z npm WARN tar ENOENT: no such file or directory,open 'D:\a\1\s\src\fightplan_v1\node_modules\.staging\primeng-e2ced65b\resources\components\toast\toast.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:\npm\cache\_logs\2018-12-11T21_47_36_496Z-debug.log
2018-12-11T21:47:36.6035543Z ##[error]npm Failed with error: C:\Program Files\nodejs\npm.cmd Failed with return code: 1
2018-12-11T21:47:36.6062198Z ##[section]Finishing: npm install

解决方法

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

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

docker npm install错误：getaddrinfo ENOTFOUND注册表.npmjs.org注册表.npmjs.org：443

docker npm install错误：getaddrinfo ENOTFOUND注册表.npmjs.org注册表.npmjs.org：443

我在RHEL 7上使用Docker版本1.10.1，在使用以下Dockerfile时出现npm install错误。错误：getaddrinfo
ENOTFOUND Registry.npmjs.org Registry.npmjs.org:443。在ubuntu 14.04上使用docker
1.91进行相同的工作。当我得到bash并在容器上安装inetutils-ping时，我注意到我无法在任何地方ping

root@9deb4b274c1e:/home/nodexp#ping 8.8.8.8           PING 8.8.8.8 (8.8.8.8): 56 data bytes^C--- 8.8.8.8 ping statistics ---4 packets transmitted, 0 packets received, 100% packet loss

这是为什么 ？我当然可以从RHEL ping

Docker文件

FROM node:argon# Create user nodexp in group nodexpRUN groupadd -r nodexp \    && useradd -m -r -g nodexp nodexpWORKDIR /home/nodexp# Install app dependenciesCOPY package.json /home/nodexpRUN npm install# Bundle app sourceCOPY . /home/nodexpEXPOSE 3000CMD [ "npm", "start" ]

和package.json

{  "name": "mp",  "version": "0.0.0",  "private": true,  "scripts": {    "start": "node app.js"  },  "dependencies": {    "express": "~4.13.1"  }}

答案1

小编典典

使用此命令重新启动docker为我修复了它，但我不知道为什么

sudo service docker restart

今天关于eslint npm 错误！ 404 未找到 - GET https://registry.npmjs.org/eslist - 未找到和未找到npm包入口文件的介绍到此结束，谢谢您的阅读，有关$ npm install eslint -g = -bash: $: 命令未找到、asp.net – 问题映射HttpHandler – > HTTP错误404未找到、azure – npm ERR！ 404未找到：har-validator@5.1.2、docker npm install错误：getaddrinfo ENOTFOUND注册表.npmjs.org注册表.npmjs.org：443等更多相关知识的信息可以在本站进行查询。

本文标签：

上一篇如何在 y 轴右侧标记 r Heatmap 中的整个组？（添加右侧坐标轴）

下一篇Oracle xmlagg 字符串缓冲区太小（oracle字符串缓冲区太小怎么解决）

相关文章