Local dev server can't be installed on Windows / ARM64

Open
#184 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
node.js, typescript
Domain
cli, devtools

Research direction

Start by reproducing the Windows/ARM64 installation with the ARM64 node distribution, focusing on the install.js step shown in the error. Verify the plugin can install on Windows ARM64 and that sf lightning dev app starts successfully there.

Written by the indexing model from the issue text.

Description

I imagine this is a bit of a corner-case, but minimally I figured it should be brought to the team's attention.

I'm in the process of integrating LWC local dev into Illuminated Cloud 2, and I also recently picked up a Surface Laptop 7 which uses ARM64 instead of x64. The Salesforce CLI's packaged Windows x64 installer works just fine, albeit a bit slowly -- it's actually much quicker to use an npm-based install which in turn uses the ARM64-native node distribution -- and the lightning-dev CLI plugin installs just fine into this x64-based CLI install. Note that it doesn't install when using the ARM64 node.exe:

npm error command failed
npm error command C:\Windows\system32\cmd.exe /d /s /c node install.js
npm error Unsupported platform: win32 arm64 LE

More on all of that here for those who might be curious.

UPDATE: The portion of the issue below was just user error, but I think it makes sense to keep this around to allow the plugin to be installed on Windows/ARM64 machines.

Anyway, when I try to start the server, I get the following:

$ sf lightning dev app
Error (1): The requested resource does not exist

Any idea what might be happening? Of course, it starts just fine on my Surface Laptop 5 which has a more traditional x64 processor.

Is there any type of verbose logging I might enable that could help to track this down?

Thanks in advance for your assistance...

Dominant language
TypeScript
Stars
19
Forks
19
Avg merge
3d 12h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from salesforcecli/plugin-lightning-dev

All issues in salesforcecli/plugin-lightning-dev

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.