Вопрос:

Установка сторонних JS-плагинов через npm INSIDE Foundation создает ошибки.

javascript npm zurb-foundation

24 просмотра

1 ответ

5 Репутация автора

Я новичок в проектах, использующих NodeJS и npm. Я возился с базовым CLI в Foundation 6.4 и пытаюсь установить сторонние плагины JS, в данном случае chart.js https://www.chartjs.org/

Итак, я бегу

npm install chart.js --save

как описано в их документации: https://www.chartjs.org/docs/latest/getting-started/installation.html

Поскольку я хочу использовать это внутри своего базового проекта, я счел целесообразным выполнить эту команду изнутри базового проекта, так сказать, «корня» всего проекта. Однако при этом я получаю огромный список ошибок при установке:

npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\postcss-selector-parser-79b1786b\package.json'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\postcss-selector-parser-79b1786b\README.md'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\postcss-selector-parser-79b1786b\CHANGELOG.md'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\source-map-resolve-22d3c721\test\common.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uniq-b6c0c289\test\test.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\svgo-d6999a75\plugins\_collections.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\source-map-resolve-22d3c721\test\read.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\source-map-resolve-22d3c721\test\source-map-resolve.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\unique-filename-73563e8d\coverage\__root__\index.html'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\unique-filename-73563e8d\coverage\__root__\index.js.html'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\jquery-e95abfa6\src\css\var\cssExpand.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\jquery-e95abfa6\src\css\var\getStyles.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\jquery-e95abfa6\src\css\var\isHiddenWithinTree.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\jquery-e95abfa6\src\css\var\rboxStyle.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\jquery-e95abfa6\src\css\var\rnumnonpx.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-proposal-unicode-property-regex-8ad643ab\src\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\jquery-e95abfa6\src\css\var\swap.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\jquery-e95abfa6\src\data.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-transform-dotall-regex-1df1d1be\lib\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-transform-dotall-regex-1df1d1be\src\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\compile\async.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-transform-dotall-regex-1df1d1be\test\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\compile\equal.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\compile\error_classes.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\compile\formats.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\compile\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\compile\resolve.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\compile\rules.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\compile\schema_obj.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\compile\ucs2length.js'
npm WARN tar ENOENT: no such file or directory, lstat 'D:\foundationtests\node_modules\.staging\@babel\plugin-proposal-unicode-property-regex-8ad643ab\test\fixtures'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\compile\util.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\ajv-89eb8fee\lib\data.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-proposal-unicode-property-regex-8ad643ab\test\fixtures\with-unicode-flag\options.json'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\fs-extra-cf94d4f2\lib\fs\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-gyp-5150d3a7\gyp\tools\Xcode\README'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\handlebars-5e0aecc8\lib\handlebars\base.js'
npm WARN tar ENOENT: no such file or directory, lstat 'D:\foundationtests\node_modules\.staging\handlebars-5e0aecc8\lib'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\parse\regex.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\parse\token.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\test\fixtures\custom-functions\setter-expected.css'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\test\fixtures\custom-functions\setter.scss'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\test\fixtures\custom-functions\string-conversion-expected.css'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\test\fixtures\custom-functions\string-conversion.scss'
npm WARN tar ENOENT: no such file or directory, lstat 'D:\foundationtests\node_modules\.staging\jsdom-afeff42d\lib\jsdom\living\xhr'
npm WARN tar ENOENT: no such file or directory, lstat 'D:\foundationtests\node_modules\.staging\jsdom-afeff42d\lib'

Кроме того, эти ошибки, похоже, меняются каждый раз, когда я выполняю установку.

D:\foundationtests>npm install --save chart.js
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\fined-0dc44eaf\package.json'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\parse-filepath-dd59234a\package.json'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\parse-filepath-dd59234a\README.md'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\fined-0dc44eaf\README.md'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\is-relative-8f0e46f4\package.json'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\is-absolute-6dc5e586\package.json'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\parse-filepath-dd59234a\LICENSE'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\fined-0dc44eaf\LICENSE'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\is-relative-8f0e46f4\README.md'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\is-absolute-6dc5e586\README.md'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\is-relative-8f0e46f4\LICENSE'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\parse-filepath-dd59234a\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\fined-0dc44eaf\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\is-relative-8f0e46f4\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\is-absolute-6dc5e586\LICENSE'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\is-absolute-6dc5e586\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\gulp-cli-b31321ab\lib\versioned\^4.0.0-alpha.2\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-proposal-unicode-property-regex-8ad643ab\lib\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-transform-dotall-regex-1df1d1be\lib\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-proposal-unicode-property-regex-8ad643ab\src\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-transform-dotall-regex-1df1d1be\src\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\src\libsass\include\sass\base.h'
npm WARN tar ENOENT: no such file or directory, lstat 'D:\foundationtests\node_modules\.staging\@babel\plugin-transform-dotall-regex-1df1d1be\test'
npm WARN tar ENOENT: no such file or directory, lstat 'D:\foundationtests\node_modules\.staging\@babel\plugin-proposal-unicode-property-regex-8ad643ab\test'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\src\libsass\include\sass\context.h'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\src\libsass\include\sass\functions.h'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-transform-dotall-regex-1df1d1be\test\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\@babel\plugin-proposal-unicode-property-regex-8ad643ab\test\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\src\libsass\include\sass\values.h'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\src\libsass\include\sass\version.h'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\src\libsass\include\sass\version.h.in'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\src\libsass\include\sass2scss.h'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\src\libsass\INSTALL'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\node-sass-e9c9e34c\src\libsass\LICENSE'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\http.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\http.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\http.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\https.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\https.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\https.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\mailto.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\mailto.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\mailto.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\urn-uuid.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\urn-uuid.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\urn-uuid.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\urn.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\urn.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\schemes\urn.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\uri.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\uri.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\uri.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\util.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\util.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\uri-js-a59e23e7\dist\esnext\util.js.map'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\fs-extra-cf94d4f2\lib\move\index.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\jquery-e95abfa6\src\queue\delay.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\browser-sync-ui-18c2e4d5\public\js\app.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\base-config.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\calendar.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\constructor.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\en.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\formats.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\invalid.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\lists.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\locale.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\locales.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\ordinal.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\pre-post-format.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\prototype.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\relative.js'
npm WARN tar ENOENT: no such file or directory, open 'D:\foundationtests\node_modules\.staging\moment-01d97eee\src\lib\locale\set.js'
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/har-validator/-/har-validator-5.1.2.tgz
npm ERR! 404
npm ERR! 404  'har-validator@5.1.2' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'foundationtests'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Когда я запускаю команду изнутри папки nodeJS, все работает нормально.

D:\nodeJS\node-v10.16.0-win-x64>npm install --save chart.js
+ chart.js@2.8.0
added 6 packages from 8 contributors in 1.403s


   ╭────────────────────────────────────────────────────────────────╮
   │                                                                │
   │      New minor version of npm available! 6.9.0 -> 6.10.2       │
   │   Changelog: https://github.com/npm/cli/releases/tag/v6.10.2   │
   │               Run npm install -g npm to update!                │
   │                                                                │
   ╰────────────────────────────────────────────────────────────────╯

Однако, что бы я ни делал, в конце концов установка и интеграция не работают. Как описано в документации и руководствах, я добавил

import Chart from 'chart.js';
var myChart = new Chart(ctx, {...});

к моему app.js моего базового проекта, но когда я перезапускаю свои фундаментальные часы, я получаю сообщение об ошибке:

[10:38:51] Error in plugin "webpack-stream"
Message:
    ./src/assets/js/app.js
Module not found: Error: Can't resolve 'chart.js' in 'D:\foundationtests\src\assets\js'
resolve 'chart.js' in 'D:\foundationtests\src\assets\js'
  Parsed request is a module
  using description file: D:\foundationtests\package.json (relative path: ./src/assets/js)
    Field 'browser' doesn't contain a valid alias configuration
    resolve as module
      D:\foundationtests\src\assets\js\node_modules doesn't exist or is not a directory
      D:\foundationtests\src\assets\node_modules doesn't exist or is not a directory
      D:\foundationtests\src\node_modules doesn't exist or is not a directory
      D:\node_modules doesn't exist or is not a directory
      looking for modules in D:\foundationtests\node_modules
        using description file: D:\foundationtests\package.json (relative path: ./node_modules)
          Field 'browser' doesn't contain a valid alias configuration
          using description file: D:\foundationtests\package.json (relative path: ./node_modules/chart.js)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              D:\foundationtests\node_modules\chart.js doesn't exist
            .wasm
              Field 'browser' doesn't contain a valid alias configuration
              D:\foundationtests\node_modules\chart.js.wasm doesn't exist
            .mjs
              Field 'browser' doesn't contain a valid alias configuration
              D:\foundationtests\node_modules\chart.js.mjs doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              D:\foundationtests\node_modules\chart.js.js doesn't exist
            .json
              Field 'browser' doesn't contain a valid alias configuration
              D:\foundationtests\node_modules\chart.js.json doesn't exist
            as directory
              D:\foundationtests\node_modules\chart.js doesn't exist
[D:\foundationtests\src\assets\js\node_modules]
[D:\foundationtests\src\assets\node_modules]
[D:\foundationtests\src\node_modules]
[D:\node_modules]
[D:\foundationtests\node_modules\chart.js]
[D:\foundationtests\node_modules\chart.js.wasm]
[D:\foundationtests\node_modules\chart.js.mjs]
[D:\foundationtests\node_modules\chart.js.js]
[D:\foundationtests\node_modules\chart.js.json]
 @ ./src/assets/js/app.js 3:0-29
 @ multi ./src/assets/js/app.js
Details:
    domain: [object Object]
    domainThrown: true

[10:38:51] 'build' errored after 13 s
[10:38:51] 'default' errored after 13 s
[10:38:51] The following tasks did not complete: images
[10:38:51] Did you forget to signal async completion?
Error: foundation-zurb-template@1.0.0 start: `gulp`
Exit status 1
    at EventEmitter.<anonymous> (D:\nodeJS\node-v10.16.0-win-x64\node_modules\foundation-cli\node_modules\npm\lib\utils\lifecycle.js:217:16)
    at EventEmitter.emit (events.js:198:13)
    at ChildProcess.<anonymous> (D:\nodeJS\node-v10.16.0-win-x64\node_modules\foundation-cli\node_modules\npm\lib\utils\spawn.js:24:14)
    at ChildProcess.emit (events.js:198:13)
    at maybeClose (internal/child_process.js:982:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)

Так что я либо делаю что-то не так во время интеграции, либо чего-то не хватает во время установки. Но я почему-то из идей, что еще я мог сделать, чтобы заставить его работать ...

РЕДАКТИРОВАТЬ: я должен добавить, что у меня нет прав администратора на машине, на которой я пытаюсь выполнить установку. Это не создавало никаких проблем с установкой Foundation ZURB Template и тому подобного, поэтому я думаю, что это не должно быть проблемой, но я просто хотел упомянуть об этом для полноты картины.

Автор: Hicksfeld Источник Размещён: 02.08.2019 08:58

Ответы (1)


0 плюса

4647 Репутация автора

Это известная ошибка / проблема в npm. Попробуйте rm -rf node_modules, попробуйте еще раз и проверьте, можете ли вы обновить npm.

Автор: Daniel Ruf Размещён: 11.08.2019 08:13
Вопросы из категории :
32x32