Can not deploy Next.js app
spiggyBe opened this issue · 1 comments
Link to the code that reproduces this issue
https://github.com/spiggyBe/ubezpieczenie-na-zycie-gliwice
To Reproduce
Reinstall npm
nom run build
Try to deploy but get an error, do not know why and how sole it
Current vs. Expected behavior
SHould deploy as my previous websites.
Provide environment information
WindowsWhich area(s) are affected? (Select all that apply)
create-next-app
Which stage(s) are affected? (Select all that apply)
Vercel (Deployed)
Additional context
[10:02:39.721] Running build in Washington, D.C., USA (East) – iad1
[10:02:39.922] Cloning github.com/spiggyBe/ubezpieczenie-na-zycie-gliwice (Branch: master, Commit: e1d80bc)
[10:02:39.941] Skipping build cache, deployment was triggered without cache.
[10:02:41.339] Cloning completed: 1.408s
[10:02:41.930] Running "vercel build"
[10:02:42.886] Vercel CLI 34.1.10
[10:02:43.876] Installing dependencies...
[10:02:54.990]
[10:02:54.991] added 370 packages in 11s
[10:02:54.991]
[10:02:54.991] 133 packages are looking for funding
[10:02:54.991] run npm fund for details
[10:02:55.017] Detected Next.js version: 12.2.1
[10:02:55.022] Detected package-lock.json generated by npm 7+
[10:02:55.023] Running "npm run build"
[10:02:55.276]
[10:02:55.278] > frontend-silesia@0.1.0 build
[10:02:55.278] > next build
[10:02:55.279]
[10:02:55.512] info - Loaded env from /vercel/path0/.env
[10:02:55.677] info - SWC minify release candidate enabled. https://nextjs.link/swcmin
[10:02:55.696] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[10:02:55.696] This information is used to shape Next.js' roadmap and prioritize features.
[10:02:55.699] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[10:02:55.699] https://nextjs.org/telemetry
[10:02:55.699]
[10:02:55.817] info - Linting and checking validity of types...
[10:02:58.067] info - Creating an optimized production build...
[10:02:58.804] info - Downloading WASM swc package...
[10:03:03.252] info - Using experimental wasm build of next-swc
[10:03:05.069] warn - Attempted to load @next/swc-linux-x64-gnu, but an error occurred: libssl.so.1.1: cannot open shared object file: No such file or directory
[10:03:05.075] warn - Attempted to load @next/swc-linux-x64-gnux32, but it was not installed
[10:03:05.076] warn - Attempted to load @next/swc-linux-x64-musl, but an error occurred: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory
[10:03:14.265] panicked at 'The global thread pool has not been initialized.: ThreadPoolBuildError { kind: IOError(Error { kind: Unsupported, message: "operation not supported on this platform" }) }', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/rayon-core-1.9.1/src/registry.rs:170:10
[10:03:14.266]
[10:03:14.266] Stack:
[10:03:14.267]
[10:03:14.267] Error
[10:03:14.267] at module.exports.__wbg_new_693216e109162396 (/vercel/path0/node_modules/next/wasm/@next/swc-wasm-nodejs/wasm.js:202:17)
[10:03:14.267] at wasm://wasm/059aa236:wasm-function[5445]:0xf90917
[10:03:14.267] at wasm://wasm/059aa236:wasm-function[13700]:0x11eca7b
[10:03:14.268] at wasm://wasm/059aa236:wasm-function[9995]:0x1186adc
[10:03:14.268] at wasm://wasm/059aa236:wasm-function[11009]:0x11b6862
[10:03:14.268] at wasm://wasm/059aa236:wasm-function[12785]:0x11e5cdd
[10:03:14.268] at wasm://wasm/059aa236:wasm-function[11383]:0x11c358f
[10:03:14.268] at wasm://wasm/059aa236:wasm-function[10017]:0x1187e72
[10:03:14.269] at wasm://wasm/059aa236:wasm-function[1151]:0x98decd
[10:03:14.269] at wasm://wasm/059aa236:wasm-function[654]:0x75f3f2
[10:03:14.269]
[10:03:14.269]
[10:03:14.828] Failed to compile.
[10:03:14.828]
[10:03:14.829] static/chunks/framework-b8fa97bf440da249.js from Terser
[10:03:14.829] unreachable
[10:03:14.829] RuntimeError: unreachable
[10:03:14.829] at wasm://wasm/059aa236:wasm-function[9995]:0x1186aff
[10:03:14.829] at wasm://wasm/059aa236:wasm-function[11009]:0x11b6862
[10:03:14.829] at wasm://wasm/059aa236:wasm-function[12785]:0x11e5cdd
[10:03:14.830] at wasm://wasm/059aa236:wasm-function[11383]:0x11c358f
[10:03:14.830] at wasm://wasm/059aa236:wasm-function[10017]:0x1187e72
[10:03:14.830] at wasm://wasm/059aa236:wasm-function[1151]:0x98decd
[10:03:14.830] at wasm://wasm/059aa236:wasm-function[654]:0x75f3f2
[10:03:14.830] at wasm://wasm/059aa236:wasm-function[654]:0x760098
[10:03:14.830] at wasm://wasm/059aa236:wasm-function[3154]:0xd6fe73
[10:03:14.830] at wasm://wasm/059aa236:wasm-function[654]:0x75f24f
[10:03:14.830]
[10:03:14.832]
[10:03:14.832] > Build failed because of webpack errors
[10:03:14.868] Error: Command "npm run build" exited with 1
[10:03:15.143]
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.
Why was this issue closed?
To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.
The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.
- If you did not provide a link or the link you provided is not valid, we will close the issue.
- If you provide a link to a private repository, we will close the issue.
- If you provide a link to a repository but not in the correct section, we will close the issue.
What should I do?
Depending on the reason the issue was closed, you can do the following:
- If you did not provide a link, please open a new issue with a link to a reproduction.
- If you provided a link to a private repository, please open a new issue with a link to a public repository.
- If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.
In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.
My repository is private and cannot make it public
In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:
- Remove any code that is not related to the issue. (pages, API routes, components, etc.)
- Remove any dependencies that are not related to the issue.
- Remove any third-party service that would require us to sign up for an account to reproduce the issue.
- Remove any environment variables that are not related to the issue.
- Remove private packages that we do not have access to.
- If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup
I did not open this issue, but it is relevant to me, what can I do to help?
Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.
I think my reproduction is good enough, why aren't you looking into it quickly?
We look into every Next.js issue and constantly monitor open issues for new comments.
However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.
Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.