You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Node versions 14 and 16, the explorer keeps exiting without any error in the logs or console.
The docker image build for node v16 fails because of npm dependencies.
Testcase error because of old ts-node version.
What did you expect to happen?
For Node versions 14 and 16,the explorer runs properly without exiting.
The docker image build for node v16 gives successful image.
Testcases should run and pass the builds by updating ts-node package.
How can we reproduce it (as minimally and precisely as possible)?
Use nvm use 14 or nvm use 16 and npm install in both explorer and client, do npm run build in client, and npm start in explorer
Observe the explorer keeps exiting.
Build a docker image by giving the node version 16.
Observe the build fails because of legacy-peer-deps issue.
Do npm run test and observe that it gives error without even running any tests
Anything else we need to know?
No response
OS version
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
The text was updated successfully, but these errors were encountered:
What happened?
For Node versions 14 and 16, the explorer keeps exiting without any error in the logs or console.
The docker image build for node v16 fails because of npm dependencies.
Testcase error because of old ts-node version.
What did you expect to happen?
For Node versions 14 and 16,the explorer runs properly without exiting.
The docker image build for node v16 gives successful image.
Testcases should run and pass the builds by updating ts-node package.
How can we reproduce it (as minimally and precisely as possible)?
nvm use 14
ornvm use 16
andnpm install
in both explorer and client, donpm run build
in client, andnpm start
in explorernpm run test
and observe that it gives error without even running any testsAnything else we need to know?
No response
OS version
The text was updated successfully, but these errors were encountered: