Apple Silicon support?

[gregbenz]

Updating to latest Node seems to break the tool.

The notes say Electron is not supported on Apple Silicon (was released Nov 2020): https://github.com/adobe-uxp/devtools-cli/blob/7b9fd6456148aecc63c002b73892df705df94267/packages/uxp-devtools-cli/README.md

Error running "uxp plugin package"
...electron-napi.node' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64'))

Are there plans to update the CLI Tool?
Which versions of Node are officially supported (without having to run Terminal under Rosetta2)?

[jardicc]

@gregbenz offtopic: were you able to run autonated UXP plugin tests via this CLI as documented in this repo?

[gregbenz]

@jardicc I never tried, as I built my own test setup earlier. You run into errors?

[jardicc]

I can't make it work at all. It showed as connected but does not run any tests. It should use WebdriverIO

What approach did you use for your tests?

[gregbenz]

It's all just custom code I wrote to quickly make sure that neither I nor some PS update broke things.

[ErinFinnegan]

Are there plans to update the CLI Tool?

We did talk about it during office hours, but unfortunately no, not at the moment.

[gregbenz]

@ErinFinnegan One downside of running Terminal under Rosetta is that it breaks yarn. Any use of yarn (even just a version check) causes Node to crash and throws "Segmentation fault: 11" in the command line.

Could you clarify which versions of Node are supported / recommended for use with the CLI tool?

[ledzepFan]

@gregbenz Node 12.19.1 is the recommended version to use.

[gregbenz]

@gregbenz Node 12.9.1 is the recommended version to use.

10 versions ago?

[jardicc]

So that should be like 5-6 years back.

[ErinFinnegan]

12.9.1 was an LTS version 2 years ago when the tool was last updated. That is the correct version.

I'm seeing if we can't at least update it to work with a more current node version.

[jardicc]

node-gyp is the issue I believe... binaries are usually a big pain and authors of good libraries/tools have some automation on their side and provide binaries by default... but with this CLI I am stuck... not sure if because of Adobe or dependencies here... but I had to install specific version of Visual Studio to be able compile C++ or C# not sure what it was. And it didn't work for me.

@ErinFinnegan you are right... I thought the typical release speed is 2 versions per year but I am wrong. https://nodejs.org/en/about/previous-releases

[mikemahony]

Hi! Any update on this?