Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm run deploy --prefix functions happen some error #51

Open
sss22213 opened this issue Dec 29, 2020 · 1 comment
Open

npm run deploy --prefix functions happen some error #51

sss22213 opened this issue Dec 29, 2020 · 1 comment

Comments

@sss22213
Copy link

HI!

when i run "npm run deploy --prefix functions", and happening problem.

node_modules/@google-cloud/firestore/types/firestore.d.ts:1629:8 - error TS2304: Cannot find name 'AsyncIterable'.

1629     ): AsyncIterable<QueryPartition<T>>;
            ~~~~~~~~~~~~~

detail:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle [email protected]~prebuild: [email protected]
6 info lifecycle [email protected]~build: [email protected]
7 verbose lifecycle [email protected]~build: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/mnt/usb2/smart-home-local/functions/node_modules/.bin:/usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/mnt/usb2/smart-home-local/functions/node_modules/.bin:/mnt/usb2/esp-idf/components/esptool_py/esptool:/mnt/usb2/esp-idf/components/espcoredump:/mnt/usb2/esp-idf/components/partition_table:/mnt/usb2/esp-idf/components/app_update:/home/an/.espressif/tools/xtensa-esp32-elf/esp-2020r3-8.4.0/xtensa-esp32-elf/bin:/home/an/.espressif/tools/xtensa-esp32s2-elf/esp-2020r3-8.4.0/xtensa-esp32s2-elf/bin:/home/an/.espressif/tools/xtensa-esp32s3-elf/esp-2020r3-8.4.0/xtensa-esp32s3-elf/bin:/home/an/.espressif/tools/esp32ulp-elf/2.28.51-esp-20191205/esp32ulp-elf-binutils/bin:/home/an/.espressif/tools/esp32s2ulp-elf/2.28.51-esp-20191205/esp32s2ulp-elf-binutils/bin:/home/an/.espressif/tools/openocd-esp32/v0.10.0-esp32-20200709/openocd-esp32/bin:/home/an/.espressif/python_env/idf4.3_py2.7_env/bin:/mnt/usb2/esp-idf/tools:/opt/sifive/JLink_Linux_V686g_x86_64:/opt/sifive/JLink_Linux_V686g_x86_64:/opt/sifive/JLink_Linux_V686g_x86_64:/opt/sifive/riscv-qemu-4.2.0-2020.04.0-x86_64-linux-ubuntu14:/opt/ros/noetic/bin:/home/an/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/an/.dotnet/tools
9 verbose lifecycle [email protected]~build: CWD: /mnt/usb2/smart-home-local/functions
10 silly lifecycle [email protected]~build: Args: [ '-c', 'tsc' ]
11 silly lifecycle [email protected]~build: Returned: code: 2  signal: null
12 info lifecycle [email protected]~build: Failed to exec build script
13 verbose stack Error: [email protected] build: `tsc`
13 verbose stack Exit status 2
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:198:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:198:13)
13 verbose stack     at maybeClose (internal/child_process.js:982:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid [email protected]
15 verbose cwd /mnt/usb2/smart-home-local/functions
16 verbose Linux 5.4.0-58-generic
17 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "run" "build"
18 verbose node v10.19.0
19 verbose npm  v6.14.10
20 error code ELIFECYCLE
21 error errno 2
22 error [email protected] build: `tsc`
22 error Exit status 2
23 error Failed at the [email protected] build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]

I have no idea to solve it.
Thanks in advance.

@proppy
Copy link
Collaborator

proppy commented Jan 21, 2021

Can you paste the output of npm ls --depth?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants