OpenZeppelin / ethernaut

Web3/Solidity based wargame
MIT License
2k stars 684 forks source link

Problems with the client when I launch it in local #736

Closed willboka closed 6 months ago

willboka commented 6 months ago

I have a compatibility issue with the recent version of the client app. I always have a error syntax issue with some JS syntax. I tried all node versions. None works for it.

I tried to use renovate/mode-16-x branch. UI launches but I can't click on any button once Imetamask is bound to it.

GianfrancoBazzani commented 6 months ago

HI @willboka can you give more context on the error showing up. have you tried with master branch?

willboka commented 6 months ago

Yes I tried with master branch with multiple versions of node (20.13 and 16.20). I have the following warning when I start the client using yarn start:ethernaut:

Starting the development server...

One of your dependencies, babel-preset-react-app, is importing the
"@babel/plugin-proposal-private-property-in-object" package without
declaring it in its dependencies. This is currently working because
"@babel/plugin-proposal-private-property-in-object" is already in your
node_modules folder for unrelated reasons, but it may break at any time.

babel-preset-react-app is part of the create-react-app project, which
is not maintianed anymore. It is thus unlikely that this bug will
ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
your devDependencies to work around this error. This will make this message
go away.

But then I have the error:

Failed to compile.

../node_modules/@truffle/contract/lib/utils/ens.js 56:35
Module parse failed: Unexpected token (56:35)
File was processed with these loaders:
 * ../node_modules/react-scripts/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|     return new ENSJS({
|       provider,
>       ensAddress: registryAddress ?? getEnsAddress(networkId)
|     });
|   },

I did all the steps in the README.md. I'm trying to run ethernaut locally.

GianfrancoBazzani commented 6 months ago

Thank you for highlighting it, @willboka. We will check it out and find a solution.