warpaltarpers/language-emojicode

Emojicode language package for Atom

language-emojicode's Issues

Not publishing

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'publish' ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session e3e0ddc0ecb94612
5 verbose publish [ '.' ]
6 info lifecycle [email protected]~prepublish: [email protected]
7 info lifecycle [email protected]~prepare: [email protected]
8 info lifecycle [email protected]~prepublishOnly: [email protected]
9 info lifecycle [email protected]~prepack: [email protected]
10 info lifecycle [email protected]~postpack: [email protected]
11 notice
12 notice package: [email protected]
13 notice === Tarball Contents ===
14 notice 449B   package.json
14 notice 443B   README.md
14 notice 10.9kB grammars/emojicode.cson
14 notice 183B   settings/language-emojicode.cson
14 notice 2.8kB  snippets/language-emojicode.cson
15 notice === Tarball Details ===
16 notice name:          language-emojicode
16 notice version:       0.1.0
16 notice package size:  3.1 kB
16 notice unpacked size: 14.7 kB
16 notice shasum:        df8fb35b44d3df6c214eaabc5b9f627391f35eb7
16 notice integrity:     sha512-muZLUCfHWbS1c[...]QBrR/2o4VB71Q==
16 notice total files:   5
17 notice
18 verbose getPublishConfig undefined
19 silly mapToRegistry name language-emojicode
20 silly mapToRegistry using default registry
21 silly mapToRegistry registry https://registry.npmjs.org/
22 silly mapToRegistry data { type: 'tag',
22 silly mapToRegistry   registry: true,
22 silly mapToRegistry   where: undefined,
22 silly mapToRegistry   raw: 'language-emojicode',
22 silly mapToRegistry   name: 'language-emojicode',
22 silly mapToRegistry   escapedName: 'language-emojicode',
22 silly mapToRegistry   scope: undefined,
22 silly mapToRegistry   rawSpec: '',
22 silly mapToRegistry   saveSpec: null,
22 silly mapToRegistry   fetchSpec: 'latest',
22 silly mapToRegistry   gitRange: undefined,
22 silly mapToRegistry   gitCommittish: undefined,
22 silly mapToRegistry   hosted: undefined }
23 silly mapToRegistry uri https://registry.npmjs.org/language-emojicode
24 verbose publish registryBase https://registry.npmjs.org/
25 silly publish uploading C:\Users\mandc\AppData\Local\Temp\npm-4004-c0bb4029\tmp\fromDir-ffad5611\package.tgz
26 verbose stack Error: EPERM: operation not permitted, unlink 'C:\Users\mandc\AppData\Local\Temp\npm-4004-c0bb4029\tmp\fromDir-ffad5611\package.tgz'
27 verbose cwd D:\Libraries\Code\language-emojicode
28 verbose Windows_NT 10.0.17134
29 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "publish"
30 verbose node v8.12.0
31 verbose npm  v6.4.1
32 error path C:\Users\mandc\AppData\Local\Temp\npm-4004-c0bb4029\tmp\fromDir-ffad5611\package.tgz
33 error code EPERM
34 error errno -4048
35 error syscall unlink
36 error Error: EPERM: operation not permitted, unlink 'C:\Users\mandc\AppData\Local\Temp\npm-4004-c0bb4029\tmp\fromDir-ffad5611\package.tgz'
36 error  { Error: EPERM: operation not permitted, unlink 'C:\Users\mandc\AppData\Local\Temp\npm-4004-c0bb4029\tmp\fromDir-ffad5611\package.tgz'
36 error   cause:
36 error    { Error: EPERM: operation not permitted, unlink 'C:\Users\mandc\AppData\Local\Temp\npm-4004-c0bb4029\tmp\fromDir-ffad5611\package.tgz'
36 error      errno: -4048,
36 error      code: 'EPERM',
36 error      syscall: 'unlink',
36 error      path: 'C:\\Users\\mandc\\AppData\\Local\\Temp\\npm-4004-c0bb4029\\tmp\\fromDir-ffad5611\\package.tgz' },
36 error   isOperational: true,
36 error   stack: 'Error: EPERM: operation not permitted, unlink \'C:\\Users\\mandc\\AppData\\Local\\Temp\\npm-4004-c0bb4029\\tmp\\fromDir-ffad5611\\package.tgz\'',
36 error   errno: -4048,
36 error   code: 'EPERM',
36 error   syscall: 'unlink',
36 error   path: 'C:\\Users\\mandc\\AppData\\Local\\Temp\\npm-4004-c0bb4029\\tmp\\fromDir-ffad5611\\package.tgz' }
37 error The operation was rejected by your operating system.
37 error It's possible that the file was already in use (by a text editor or antivirus),
37 error or that you lack permissions to access it.
37 error
37 error If you believe this might be a permissions issue, please double-check the
37 error permissions of the file and its containing directories, or try running
37 error the command again as root/Administrator (though this is not recommended).
38 verbose exit [ -4048, true ]