cli icon indicating copy to clipboard operation
cli copied to clipboard

Published 20 hours ago • verified publisher icon netlify

Wasm Error

Open danisztls opened this issue 3 years ago • 5 comments

Describe the bug

The following appear each time I run netlify-cli:

wasm streaming compile failed: TypeError: Failed to parse URL from /home/user/.local/share/npm/lib/node_modules/netlify-cli/node_modules/netlify-redirector/lib/redirects.wasm
falling back to ArrayBuffer instantiation

Steps to reproduce

Run netlify status.

Configuration

None.

Environment

System: OS: Linux 5.17 Arch Linux CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor Memory: 6.53 GB / 15.61 GB Container: Yes Shell: 5.8.1 - /bin/zsh Binaries: Node: 18.1.0 - /bin/node Yarn: 1.22.18 - /bin/yarn npm: 8.5.5 - /bin/npm npmGlobalPackages: netlify-cli: 10.3.1

danisztls avatar May 13 '22 18:05 danisztls

Same error on OSX 12.3.1 with Node 18.2.0 and neltify-cli 10.3.3.

johnloy avatar May 27 '22 12:05 johnloy

I've been gettting the same error.

arpit-agr avatar Jul 07 '22 08:07 arpit-agr

Same error here, is it recommended to downgrade node or netlify-cli?

RossellaFer avatar Jul 09 '22 12:07 RossellaFer

@johnloy @arpit-agr I downgraded node to 16.0.0 and it now works!

RossellaFer avatar Jul 11 '22 07:07 RossellaFer

@RossellaFer Downgrading might work but isn't a solution.

danisztls avatar Jul 12 '22 23:07 danisztls

I was able to reproduce this issue by following the tutorial section of netlify: https://docs.netlify.com/get-started/ using node v18. the function section would not work.

after downgrading to v16 the local dev would then work properly.

Agree with @danisztls that fixing the issue with out the need to downgrade should be the right path forward

gltovar avatar Aug 12 '22 09:08 gltovar

Related: https://github.com/netlify/cli/issues/4625#issuecomment-1137701649

tinfoil-knight avatar Aug 23 '22 07:08 tinfoil-knight

This is already fixed on the main branch and the warning will disappear with the next version of the cli.

danez avatar Aug 26 '22 14:08 danez

How was this fixed?

Anutrix avatar Nov 14 '23 09:11 Anutrix

How I fixed it on my side:

  • double-checked that I do not have several global netlify-cli packages installed (NPM, yarn, PNPM, bun)
  • removed all of the installed ones + realized that I had some remaining in /usr/local/bin since I'm running Ubuntu (those were taking prio over other package managers)
    • there I deleted both ntl and netlify (double checking that I have nothing installed thanks to whereis)
  • used nvm to install node v20.10.0 (got some issues with v20.9)
  • npm install -g [email protected] to have the same working version as on my Macbook

This went from failing to launch a local Nuxt2 app, to having a successful (even tho a bit slower) start of my Nuxt3 app (is actually a Nuxt3 one, the CLI was trying to launch both Nuxt v2 and v3 before probably because I got the v9 of the CLI haha).

Maybe this could be helpful. 😸

kissu avatar Jan 13 '24 16:01 kissu