Начинающий Python программист

При установке SASS на macOS вываливаются ошибки. Как решить?


Логи прикладываю)
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'install',
1 verbose cli '-g',
1 verbose cli 'sass'
1 verbose cli ]
2 info using npm@6.14.13
3 info using node@v14.17.0
4 verbose npm-session 4a40fb180bc39c06
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/sass 257ms (from cache)
8 silly pacote tag manifest for sass@latest fetched in 268ms
9 timing stage:loadCurrentTree Completed in 281ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 2ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule sass@1.34.1 checking installable status
17 http fetch GET 304 https://registry.npmjs.org/chokidar 76ms (from cache)
18 silly pacote range manifest for chokidar@>=3.0.0 <4.0.0 fetched in 79ms
19 silly resolveWithNewModule chokidar@3.5.1 checking installable status
20 http fetch GET 304 https://registry.npmjs.org/anymatch 184ms (from cache)
21 silly pacote range manifest for anymatch@~3.1.1 fetched in 186ms
22 silly resolveWithNewModule anymatch@3.1.2 checking installable status
23 http fetch GET 304 https://registry.npmjs.org/is-glob 234ms (from cache)
24 silly pacote range manifest for is-glob@~4.0.1 fetched in 235ms
25 silly resolveWithNewModule is-glob@4.0.1 checking installable status
26 http fetch GET 304 https://registry.npmjs.org/fsevents 252ms (from cache)
27 silly pacote range manifest for fsevents@~2.3.1 fetched in 256ms
28 silly resolveWithNewModule fsevents@2.3.2 checking installable status
29 http fetch GET 304 https://registry.npmjs.org/glob-parent 264ms (from cache)
30 http fetch GET 304 https://registry.npmjs.org/readdirp 259ms (from cache)
31 http fetch GET 304 https://registry.npmjs.org/braces 268ms (from cache)
32 silly pacote range manifest for glob-parent@~5.1.0 fetched in 268ms
33 silly resolveWithNewModule glob-parent@5.1.2 checking installable status
34 silly pacote range manifest for readdirp@~3.5.0 fetched in 262ms
35 silly resolveWithNewModule readdirp@3.5.0 checking installable status
36 silly pacote range manifest for braces@~3.0.2 fetched in 271ms
37 silly resolveWithNewModule braces@3.0.2 checking installable status
38 http fetch GET 304 https://registry.npmjs.org/is-binary-path 268ms (from cache)
39 silly pacote range manifest for is-binary-path@~2.1.0 fetched in 270ms
40 silly resolveWithNewModule is-binary-path@2.1.0 checking installable status
41 http fetch GET 304 https://registry.npmjs.org/normalize-path 297ms (from cache)
42 silly pacote range manifest for normalize-path@~3.0.0 fetched in 298ms
43 silly resolveWithNewModule normalize-path@3.0.0 checking installable status
44 http fetch GET 304 https://registry.npmjs.org/picomatch 63ms (from cache)
45 silly pacote range manifest for picomatch@^2.0.4 fetched in 67ms
46 silly resolveWithNewModule picomatch@2.3.0 checking installable status
47 http fetch GET 304 https://registry.npmjs.org/fill-range 67ms (from cache)
48 silly pacote range manifest for fill-range@^7.0.1 fetched in 68ms
49 silly resolveWithNewModule fill-range@7.0.1 checking installable status
50 http fetch GET 304 https://registry.npmjs.org/to-regex-range 63ms (from cache)
51 silly pacote range manifest for to-regex-range@^5.0.1 fetched in 65ms
52 silly resolveWithNewModule to-regex-range@5.0.1 checking installable status
53 http fetch GET 200 https://registry.npmjs.org/is-number 5ms (from cache)
54 silly pacote range manifest for is-number@^7.0.0 fetched in 6ms
55 silly resolveWithNewModule is-number@7.0.0 checking installable status
56 http fetch GET 304 https://registry.npmjs.org/is-extglob 82ms (from cache)
57 silly pacote range manifest for is-extglob@^2.1.1 fetched in 84ms
58 silly resolveWithNewModule is-extglob@2.1.1 checking installable status
59 http fetch GET 304 https://registry.npmjs.org/binary-extensions 66ms (from cache)
60 silly pacote range manifest for binary-extensions@^2.0.0 fetched in 67ms
61 silly resolveWithNewModule binary-extensions@2.2.0 checking installable status
62 timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 768ms
63 timing stage:loadIdealTree Completed in 776ms
64 silly currentTree lib
65 silly idealTree lib
65 silly idealTree └─┬ sass@1.34.1
65 silly idealTree ├── anymatch@3.1.2
65 silly idealTree ├── binary-extensions@2.2.0
65 silly idealTree ├── braces@3.0.2
65 silly idealTree ├── chokidar@3.5.1
65 silly idealTree ├── fill-range@7.0.1
65 silly idealTree ├── fsevents@2.3.2
65 silly idealTree ├── glob-parent@5.1.2
65 silly idealTree ├── is-binary-path@2.1.0
65 silly idealTree ├── is-extglob@2.1.1
65 silly idealTree ├── is-glob@4.0.1
65 silly idealTree ├── is-number@7.0.0
65 silly idealTree ├── normalize-path@3.0.0
65 silly idealTree ├── picomatch@2.3.0
65 silly idealTree ├── readdirp@3.5.0
65 silly idealTree └── to-regex-range@5.0.1
66 silly install generateActionsToTake
67 warn checkPermissions Missing write access to /usr/local/lib/node_modules
68 timing stage:rollbackFailedOptional Completed in 1ms
69 timing stage:runTopLevelLifecycles Completed in 1063ms
70 verbose stack Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
71 verbose cwd /Users/user
72 verbose Darwin 20.5.0
73 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "sass"
74 verbose node v14.17.0
75 verbose npm v6.14.13
76 error code EACCES
77 error syscall access
78 error path /usr/local/lib/node_modules
79 error errno -13
80 error Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
80 error [Error: EACCES: permission denied, access '/usr/local/lib/node_modules'] {
80 error errno: -13,
80 error code: 'EACCES',
80 error syscall: 'access',
80 error path: '/usr/local/lib/node_modules'
80 error }
81 error The operation was rejected by your operating system.
81 error It is likely you do not have the permissions to access this file as the current user
81 error
81 error If you believe this might be a permissions issue, please double-check the
81 error permissions of the file and its containing directories, or try running
81 error the command again as root/Administrator.
82 verbose exit [ -13, true ]
  • Вопрос задан
  • 23 просмотра
Пригласить эксперта
Ответы на вопрос 1
Написано же нет прав на каталог. Sudo поидее поможет...
Ответ написан
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы