No native build was found for platform=darwin arch=arm64 runtime=node abi=115 uv=1 armv=8 libc=glibc
Unanswered
Ojos Azules posted this in #help-forum
Ojos AzulesOP
Can anyone help me with this error
47 Replies
Toyger
some installed dependency don't have support of arm64, can you provide full output, maybe there are will be some detailed info.
@Toyger some installed dependency don't have support of arm64, can you provide full output, maybe there are will be some detailed info.
Ojos AzulesOP
full output as in what is coming in terminal?
Ojos AzulesOP
this is the complete output
when i compile my code everytime
Toyger
no, not only error, but whole output from beggining, it definitely should be bigger
this is the error when i start to compile from beginning
Toyger
can you check path from error
.next/server/vendor-chunks is it file or folder, if file can you copy it here, if folder maybe screenshot of contentsOjos AzulesOP
this is for the 1st error â˜ï¸
this is for the 2nd error 👇
.next/server/webpack-runtime.js
@Ojos Azules Click to see attachment
Toyger
wdym, both of them point to
.next/server/vendor-chunks so it should be either one file or folderidk what "loaded from: <path> at <path>" means
Toyger
no, it should be
.next/server/vendor-chunks itself@Toyger no, it should be `.next/server/vendor-chunks` itself
Ojos AzulesOP
its an entire folder
Toyger
can you screshot it, list of files
@Ojos Azules this is for the 2nd error 👇
Ojos AzulesOP
this is
webpack-runtime.js fileToyger
yeah I understood, I need screenshot of files inside vendor-chunks
Toyger
I dont need that
I asked for list of files inside
vendor-chunksonly list, not content
@Ojos Azules Click to see attachment
Ojos AzulesOP
.
@Ojos Azules .
Toyger
it's files from
/.next/server/ not an /.next/server/vendor-chunks/Ojos AzulesOP
ok
one min
Toyger
ok, it will take some time to figure out which one fails, also can you send your package.json
@Toyger ok, it will take some time to figure out which one fails, also can you send your package.json
Ojos AzulesOP
{
"name": "web5-hackathon",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
},
"pkg": {
"outputPath": ".dist",
"targets": [
"node18-win-x64",
"node18-macos-x64",
"node18-linux-x64"
],
"assets": [
"utils/*",
"public/*",
"public/**/*"
]
},
"dependencies": {
"@radix-ui/react-avatar": "^1.0.4",
"@radix-ui/react-dialog": "^1.0.5",
"@radix-ui/react-label": "^2.0.2",
"@radix-ui/react-popover": "^1.0.7",
"@radix-ui/react-radio-group": "^1.1.3",
"@radix-ui/react-select": "^2.0.0",
"@radix-ui/react-slot": "^1.0.2",
"@radix-ui/react-tabs": "^1.0.4",
"@web5/api": "^0.8.3",
"@web5/crypto": "^0.2.4",
"class-variance-authority": "^0.7.0",
"clsx": "^2.0.0",
"crypto-browserify": "^3.12.0",
"date-fns": "^3.0.6",
"formik": "^2.4.5",
"framer-motion": "^10.16.16",
"fuse.js": "^7.0.0",
"lucide-react": "^0.302.0",
"next": "14.0.4",
"next-themes": "^0.2.1",
"react": "^18",
"react-day-picker": "^8.10.0",
"react-dom": "^18",
"react-icons": "^4.12.0",
"react-tag-input-component": "^2.0.2",
"stream-browserify": "^3.0.0",
"tailwind-merge": "^2.2.0",
"tailwindcss-animate": "^1.0.7",
"yup": "^1.3.3"
},
"devDependencies": {
"@types/node": "^20",
"@types/react": "^18",
"@types/react-dom": "^18",
"autoprefixer": "^10.0.1",
"eslint": "^8",
"eslint-config-next": "14.0.4",
"postcss": "^8",
"prettier": "^3.1.1",
"prettier-plugin-tailwindcss": "^0.5.9",
"tailwindcss": "^3.3.0",
"typescript": "^5"
}
}@Toyger ok, it will take some time to figure out which one fails, also can you send your package.json
Ojos AzulesOP
can i somehow make nextjs ignore this error
i just need to successfully deploy it in vercel
@Ojos Azules can i somehow make nextjs ignore this error
Toyger
for now it show problem that some dependency don't have binary for your ARM mac architecture, nextjs use x86_x64-linux, so there is a chance that there will be 0 errors when you deploy on vercel.
@Ojos Azules i get this in vercel deployment
Toyger
as far as I understand
but at linux it should be ok, which is strange why it not working with vercel,
theoretically you can try to downgrade nodejs version, maybe it will help.
"@web5/api": "^0.8.3", relies on level@8.0.0 which relies on classic-level@1.3.0 which have problems with Mac ARMbut at linux it should be ok, which is strange why it not working with vercel,
theoretically you can try to downgrade nodejs version, maybe it will help.
@Toyger as far as I understand `"@web5/api": "^0.8.3",` relies on `level@8.0.0` which relies on `classic-level@1.3.0` which have problems with Mac ARM
but at linux it should be ok, which is strange why it not working with vercel,
theoretically you can try to downgrade nodejs version, maybe it will help.
Ojos AzulesOP
can you tell me a small overview in short as to how can i downgrade the node version for this project and deploy to vercel
@Toyger as far as I understand `"@web5/api": "^0.8.3",` relies on `level@8.0.0` which relies on `classic-level@1.3.0` which have problems with Mac ARM
but at linux it should be ok, which is strange why it not working with vercel,
theoretically you can try to downgrade nodejs version, maybe it will help.
Ojos AzulesOP
and thanks for taking time to figure it out. i'll communicate the issue to the developers of web5
@Ojos Azules can you tell me a small overview in short as to how can i downgrade the node version for this project and deploy to vercel
Toyger
at vercel it should be section where you can choose version https://vercel.com/changelog/node-js-version-now-customizable-in-the-project-settings
@Toyger at vercel it should be section where you can choose version https://vercel.com/changelog/node-js-version-now-customizable-in-the-project-settings
Ojos AzulesOP
okay understood.
thanks a lot
thanks a lot