-
Notifications
You must be signed in to change notification settings - Fork 868
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to build neoConverse app #12728
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging |
This works fine on a VM running Ubuntu. This is why I suspect it is a WSL issue. |
@jocon-grmtx on Build output:
WSL info:
|
@jocon-grmtx if the error is triggered by |
Windows Version
Microsoft Windows [Version 10.0.19045.5608]
WSL Version
2.4.11.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.167.4-1
Distro Version
Ubuntu 20.04
Other Software
I am trying to follow the instructions to deploy neoConverse (https://github.com/neo4j-labs/neoconverse)
locally on my wsl2 ubuntu, but get the issue below after multiple tries. I've tried many things - updated wsl, ubuntu, tried the dev branch, upgraded node.js. No matter what, always this issue. Can anyone please assist - give me some hints? I've even tried deploying on a separate wsl 2 machine. Same. Thanks, John
Repro Steps
`neoconverse[deploy-branch !]$ sudo npm run build
/home/jac/projects/neoconverse/node_modules/next/dist/lib/picocolors.js:134
const { env, stdout } = ((_globalThis = globalThis) == null ? void 0 : _globalThis.process) ?? {};
^
SyntaxError: Unexpected token ?
at Module._compile (internal/modules/cjs/loader.js:723:23)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at Module.mod.require (/home/jac/projects/neoconverse/node_modules/next/dist/server/require-hook.js:64:28)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. (/home/jac/projects/neoconverse/node_modules/next/dist/build/output/log.js:55:21)
at Module._compile (internal/modules/cjs/loader.js:778:30)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @1.0.0 build:
next build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2025-03-19T18_31_14_315Z-debug.log
neoconverse[deploy-branch !]$ node -v
v22.14.0
neoconverse[deploy-branch !]$ npm -v
11.2.0`
Expected Behavior
Ability to execute the app
Actual Behavior
Fails during build
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: