Skip to content
This repository was archived by the owner on May 31, 2021. It is now read-only.

Not able to make it work #345

Open
dinkargupta opened this issue Mar 25, 2021 · 2 comments
Open

Not able to make it work #345

dinkargupta opened this issue Mar 25, 2021 · 2 comments

Comments

@dinkargupta
Copy link

Followed simple steps..

  • cloned it (tried both truck and v2-release branch)
  • just ran docker-compose up
  • also tried local npm hacks.. install, update, --legacy-peer-dep (even npm-check-updates and ncu -u etc). but the project seems to be left behind the numerous dependencies that have moved on since the last update. Or I am making some stupid mistake which is causing this.. either way.. it's been two hours now with multiple google searches :-)

There is not fixed pattern .. some runs break on node.js incompatibility, some underlaying g++ compilation, some on wdio-webpack-service, some on webpack...

On my macbook... here'e the node env.
Atlas2: '2.0.4',
npm: '7.7.4',
node: '15.12.0',
v8: '8.6.395.17-node.27',
uv: '1.41.0',
zlib: '1.2.11',
brotli: '1.0.9',
ares: '1.17.1',
modules: '88',
nghttp2: '1.42.0',
napi: '8',
llhttp: '2.1.3',
openssl: '1.1.1j+quic',
cldr: '38.1',
icu: '68.2',
tz: '2020d',
unicode: '13.0'

has anyone tried this in 2021 and made it work ?

@cdaniel
Copy link
Collaborator

cdaniel commented Mar 25, 2021

Nope. I do not think anyone tried it.

It has been 2-3 years since I have not been able to maintain the project.

@dinkargupta
Copy link
Author

Thanks! Let me take a shot at it locally first.. to be honest the whole npm thing is a depedenecy hell :-) I am also not a node expert, more of a java guy but will give it a shot.. will get back if I am able to solve it and then can contribute back

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants