Failed to Compile

[JesusDeveloperX1]

After following these initial comands:
ganache-cli --deterministic (other terminal)
openzeppelin init
cd client npm run start

I got this: ( Using: Windows 10 OS / NodeJs Command Prompt / Node.js v12.10.0. / truffle@5.0.41 / ganache-cli@6.7.0 / @openzeppelin/cli@2.5.3).

Failed to compile.
./node_modules/@openzeppelin/network/react/useWeb3Hook.js
Module not found: Can't resolve '../context/Web3Context' in 'C:\Users\dimit\Projects\OpenZeppelinSDK\Starter\client\node_modules@openzeppelin\network\react'

Please help!

[JesusDeveloperX1]

I have been looking around and realized that:

1. Module "context/Web3Context" is under "lib"
2. It is required inside "useWeb3Hook.js" via a call to "../context/Web3Context" instead of "../lib/context/Web3Context"
3. Once it is corrected it gives me other errors of the same type...

Do I need to go reviewing all these errors? Are they going to end... is there a bigger hack that I`m missing here?

[JesusDeveloperX1]

I remembered that when I was installing truffle@5.0.41, ganache-cli@6.7.0, @openzeppelin/cli@2.5.3 the command "ls" to two react directories was not accomplished (executed) (Running Windows...).
Is it possible that these errors belong to this not accomplished step. If it was, how can I LS on Windows that command?

[JesusDeveloperX1]

This was the error I had in the very beginning:
"ln -s ./lib/react ./react 'ln' is not recognized as an internal or external command"
Is it possible to be the src of the error I had?

[abcoathup]

Hi @dimitrileite,

Sorry to hear that you are having issues.

You may want to look at using Windows Subsystem for Linux (WSL) https://docs.microsoft.com/en-us/windows/wsl/about
I use WSL on Windows 10 and have far fewer issues than when I was doing smart contract development on Windows (7).

I recommend for support questions to ask in the Community Forum: https://forum.openzeppelin.com/ so that the entire community can answer.

Which starter kit were you using?

At what point did you get the error: "ln -s ./lib/react ./react 'ln' is not recognized as an internal or external command".

[ylv-io]

Hey @dimitrileite. Sorry to hear about your poor experience.
Can you try to import react hooks in the following way:

import { useWeb3Injected, useWeb3Network } from '@openzeppelin/network/lib/react';

at App.js.

Let me know how it goes!

[JesusDeveloperX1]

I'm sorry @yly-io for the late response back. I was on another project. I'll try what you said and get back to you soon.

[abcoathup]

OpenZeppelin Network.js uses preinstall to create a symlink for React.
ln doesn't exist on Windows.
https://github.com/OpenZeppelin/openzeppelin-network.js/blob/master/package.json#L14

An alternative to using Windows Subsystem for Linux is to try installing with Git Bash terminal: OpenZeppelin/openzeppelin-network.js#26 (comment)

I have created an Issue for OpenZeppelin Network.js to support Windows installation: OpenZeppelin/openzeppelin-network.js#27

[hydris-bessa]

Hi @ylv-io , I just encountered the same error while tracking Dapp's setup with GSN (https://docs.openzeppelin.com/learn/sending-gasless-transactions).
I'm on WSL.
And after using the command:

1. ln -ns ../../build
2. npm start

Output :
Failed to compile
./src/App.js
Module not found: Can't resolve '@openzeppelin/network/lib/react' in '/home/hydris/blockchain/gsn-dapp/client/src'.

Can you help me with this problem?

[ylv-io]

Hm. Strange. Have you run npm install inside client folder? Can you check that react folder exists at path client/node_modules/@openzeppelin/network/lib/react?

[abcoathup]

Hi @hydris-bessa,
I have answered your question in the forum: https://forum.openzeppelin.com/t/gsn-starter-kit-module-not-found-cant-resolve-openzeppelin-network-lib-react/2810

@ylv-io I haven't had it myself, but community members occasionally report issues with the creation of the soft link (not just on Windows).

[hydris-bessa]

Thank you @abcoathup and @ylv-io for your answer.

I had to reinstall all the packages.
There was a problem with the installation of @openzeppelin/network. Some components did not install correctly which prevented the import from App.js