question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"@next/swc-android-arm64 not accessible from next" when running npm ci in Github Action

See original GitHub issue

What version of Next.js are you using?

12.0.2

What version of Node.js are you using?

14.17.1

What browser are you using?

Chrome

What operating system are you using?

Windows

How are you deploying your application?

Vercel

Describe the Bug

We’re using a Github Action to install all depencies using npm ci and deploy to Chromatic. However, this Action is failing at the moment with the following error: npm ERR! @next/swc-android-arm64 not accessible from next Running npm ci on my local machine seems to work fine. I already tried to delete the package-lock.json and recreating it but the problem still persists. We’re using npm@8.1.2 maybe it’s related to that, it appears to work fine with npm@6

Expected Behavior

npm ci installs all dependencies without any issues

To Reproduce

  • Create a Next Project with next@11 or next@12
  • Use npm@8 on your local machine
  • Run npm ci using Github Action

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:15 (6 by maintainers)

github_iconTop GitHub Comments

10reactions
charkourcommented, Dec 1, 2021

For those getting this error in their GitHub Action pipeline or other CI pipelines, make sure that your local version of npm matches the version used in by your workflow runner.

For me, I have to run the command npm i -g npm@latest in my GitHub Action .yml file to use version 8 of npm. You get this error @next/swc-android-arm64 not accessible from next if you are not running version 8 of npm.

4reactions
alejandronanezcommented, Nov 8, 2021

Updating from 12.0.2 to 12.0.3 fixed the issue for me. 👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

Next failed to load SWC binary - Stack Overflow
This error occurs because next js uses a Rust-based compiler to compile JavaScript which is much faster than babel but this is not...
Read more >
npm ERR! esbuild-android-arm64 not accessible from esbuild
npm ERR! esbuild-android-arm64 not accessible from esbuild ... npm (from package-lock.json) 2021-11-24T20:04:05.865344780Z Running npm ci ...
Read more >
@next/swc-android-arm64 - npm
Start using @next/swc-android-arm64 in your project by running `npm i @next/swc-android-arm64`. There are 3 other projects in the npm ...
Read more >
CI/CD in Node.js with GitHub Actions - LogRocket Blog
When a code is committed to a repository, it can be built and tested against setup workflows to ensure that the code does...
Read more >
Deploy your Next.js application on Vercel using Sentry and ...
We will use Github Action to handle the Continuous Integration and Sentry to ... npx create-next-app prod-ready-nextjs-sentry --use-npm.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found