Error: The package "esbuild-darwin-64" could not be found, and is needed by esbuild.

[aberllin]

Description

When attempting to run any test from the project, the error appears Error: The package "esbuild-darwin-64" could not be found, and is needed by esbuild. I already tried to install it, also tried to reinstall packages etc. Event reset mac completely.

URL of Issue(s)

Steps to replicate

I am not sure what could be the steps to reproduce since it even does work on my colleagues' machines. It was also working on mine (macOs m1) until it stopped at one point.

Browser

Google Chrome

Device

• PC
• Mac
• iPhone
• iPad
• Android Phone
• Android Tablet

Additional Information

The error in the browser:

Running npm install esbuild-darwin-64 throws an error:

npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for esbuild-darwin-64@0.15.18: wanted {"os":"darwin","arch":"x64"} (current: {"os":"darwin","arch":"arm64"})
npm ERR! notsup Valid OS:    darwin
npm ERR! notsup Valid Arch:  x64
npm ERR! notsup Actual OS:   darwin
npm ERR! notsup Actual Arch: arm64

[MikeMcC399]

@aberllin

I'm afraid that you are in the wrong place with this issue, for which you also just asked for help on https://discord.com/channels/755913899261296641/1138466874657603645

This issue list is for problems with the Cypress documentation, not for problems with Cypress software as such.

I would suggest that you be a little patient and wait to see if there are other macOS users who can assist you on Discord. Since you write that it works on co-workers' machines, then it is less likely to be a bug and more likely to be a setup issue on your machine.

[DevJSter]

It looks like you're facing an issue related to the "esbuild" package and its compatibility with your macOS M1 (arm64) architecture. The error message you provided indicates that the "esbuild-darwin-64" package is not compatible with the arm64 architecture, which is what your Mac M1 uses.

The "esbuild" package is a popular JavaScript bundler and minifier, often used for optimizing code in projects. The error you're encountering occurs because the specific version of "esbuild-darwin-64" you're trying to install is built for the x64 architecture, while your Mac M1 uses the arm64 architecture.

Here are a few steps you can try to resolve this issue:

1. Update Node.js and npm: Ensure that you're using the latest version of Node.js and npm. Sometimes, newer versions of packages might have resolved compatibility issues with specific architectures.

2. Check esbuild Updates: Verify if there's a newer version of the "esbuild" package available that supports the arm64 architecture. Developers often update packages to include compatibility for newer platforms.

3. Check Project Dependencies: Ensure that your project's dependencies are up-to-date and compatible with your architecture. Some other package you're using might be indirectly causing this issue.

4. Contact Package Maintainers: If there's no updated version available that supports the arm64 architecture, consider reaching out to the maintainers of the "esbuild" package to report the compatibility issue on macOS M1. They might be working on a fix or have suggestions for a workaround.

5. Use Rosetta 2: As a temporary solution, you can run Node.js through Rosetta 2, which is a translation layer that allows x64 binaries to run on Apple's arm64 architecture. To do this, open your terminal and run:

   arch -x86_64 /usr/local/bin/node

   Replace /usr/local/bin/node with the actual path to your Node.js binary.

6. Check Project Configuration: Double-check your project's configuration files to make sure there aren't any hardcoded references to the "esbuild-darwin-64" package or its architecture.

7. Clean Cache: Sometimes, cache issues can cause unexpected errors. Try running the following commands to clear the npm cache and then install the package again:

   npm cache clean --force
   npm install

Remember that compatibility issues like this can sometimes be challenging to resolve, especially if there's no immediate fix or workaround available from the package maintainers. It's important to keep an eye out for updates and community discussions regarding compatibility on macOS M1.

[MikeMcC399]

This issue has been discussed in Discord https://discord.com/channels/755913899261296641/1138466874657603645 and it does not seem like it is a Cypress issue. It's more likely that node_modules have been committed or otherwise moved from one architecture to another and that this is causing the error message.

@aberllin

Would you like to close this now? It's not a Cypress documentation issue anyway.

@DevJSter

It looks like you have posted an answer you received from ChatGPT or some other AI tool. Is that correct?

[aberllin]

I closed it, thank you very much!

[vincentwinkel]

What is the issue and how to fix it? I dont want to create an account on Discord to fix this issue...

[MikeMcC399]

@vincentwinkel

What is the issue and how to fix it? I dont want to create an account on Discord to fix this issue...

This isn't a Cypress issue or a Cypress documentation issue and the previous analysis pointed to

It's more likely that node_modules have been committed or otherwise moved from one architecture to another and that this is causing the error message.

Discord doesn't say any more than that.

Try deleting node_modules and if that doesn't help, then use the resources available from https://esbuild.github.io/.

Good luck!