yabukiY
Deno16mo ago
4 replies
yabuki

I couldn't install 'deno install --allow-scripts=npm:esbuild@0.21.5'

I tried to work with create-vite on deno 2.0.0-rc.4

Version: Deno 2.0.0-rc.4

OS:Debian GNU/Linux
Environment:In the LXC(incus) container.

$ deno run -A --node-modules-dir=auto npm:create-vite@latest
✔ Project name: … react-app
✔ Select a framework: › React
✔ Select a variant: › TypeScript

Scaffolding project in /home/yabuki/src/etude-react/second/react-app...

Done. Now run:

  cd react-app
  npm install
  npm run dev

then I did cd react-app and
deno install


$ deno install
Warning Following packages contained npm lifecycle scripts (preinstall/install/postinstall) that were not executed:
┠─ npm:esbuild@0.21.5
┃
┠─ This may cause the packages to not work correctly.
┗─ To run lifecycle scripts, use the `--allow-scripts` flag with `deno install`:
   deno install --allow-scripts=npm:esbuild@0.21.5

Ok. I'll follow your instructions.
$ deno install --allow-scripts=npm:esbuild@0.21.5
Error launching 'deno': Argument list too long (os error 7)
error: script 'postinstall' in 'esbuild@0.21.5' failed with exit code 1

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: deno::npm::managed::resolvers::local::sync_resolution_with_fs::{{closure}}
   2: <deno::npm::managed::resolvers::local::LocalNpmPackageResolver as deno::npm::managed::resolvers::common::NpmPackageFsResolver>::cache_packages::{{closure}}
   3: deno::npm::managed::ManagedCliNpmResolver::cache_packages::{{closure}}
   4: deno::tools::registry::pm::cache_deps::cache_top_level_deps::{{closure}}
   5: deno::spawn_subcommand::{{closure}}
   6: <deno_unsync::tokio::task::MaskFutureAsSend<F> as core::future::future::Future>::poll
   7: tokio::runtime::task::raw::poll
   8: deno::main
   9: std::sys_common::backtrace::__rust_begin_short_backtrace
  10: std::rt::lang_start::{{closure}}
  11: std::rt::lang_start_internal
  12: main
  13: <unknown>
  14: __libc_start_main
  15: _start


Is this a bug?
Was this page helpful?