Error when running the project 'Unable to resolve path to module'

[fluturecode]

Describe the bug

After running [yarn start] and error occurs flagging the 'import/no-unresolved' lint error.

Expected behavior

The project should run with no errors.

To Reproduce

Steps to reproduce the behavior:

1. Pull from Development.
2. Run [yarn start]

Screenshots

[michaelachrisco]

Im wondering if the node_modules are not pulling in the correct dependencies/modules?

Can you try to reinstall yarn via yarn install or just yarn?

If that doesn't work and you get the same error, try removing node_modules and reinstalling from there. If you are still having issues. If after all that, we may need to take a look at node version and npx.

Ill attempt the same with a blank repo and see if I get the same error.

[michaelachrisco]

Brand new repo, im getting the following error:

$ yarn start
yarn run v1.22.5
warning ../package.json: No license field
$ cross-env PORT=4200 react-scripts start
/bin/sh: 1: cross-env: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Im going to try and installing cross-env and see what pops up.

[michaelachrisco]

Ah cross-env is in devDependencies. We should probably move that to dependencies if its to get the start operation working.

[michaelachrisco]

Interesting! So when I tried to install the dependencies for the repo, it looks like if you have NODE_ENV=production then yarn does not install the devDependencies but if you have NODE_ENV=develop or anything other than production, the devDependencies get installed. I had no idea this was a thing.

Relevant documentation here: yarnpkg/yarn#2739

Can you try this?

NODE_ENV=develop
yarn
yarn start

This should be added to the repo. I would expect yarn start to have everything it needs from the base install rather than using devDependencies. We will need to change that in the package.json.

[fluturecode]

Im wondering if the node_modules are not pulling in the correct dependencies/modules?

Can you try to reinstall yarn via yarn install or just yarn?

If that doesn't work and you get the same error, try removing node_modules and reinstalling from there. If you are still having issues. If after all that, we may need to take a look at node version and npx.

Ill attempt the same with a blank repo and see if I get the same error.

Yes I had tried that and it didn't help.

[fluturecode]

Interesting! So when I tried to install the dependencies for the repo, it looks like if you have NODE_ENV=production then yarn does not install the devDependencies but if you have NODE_ENV=develop or anything other than production, the devDependencies get installed. I had no idea this was a thing.

Relevant documentation here: yarnpkg/yarn#2739

Can you try this?

NODE_ENV=develop
yarn
yarn start

This should be added to the repo. I would expect yarn start to have everything it needs from the base install rather than using devDependencies. We will need to change that in the package.json.

Ok so I will make a PR for this today.

[fluturecode]

NODE_ENV=develop

Where should I add this for documentation?

[michaelachrisco]

NODE_ENV=develop

Where should I add this for documentation?

Im not sure. I would expect yarn install to contain everything needed to do yarn start without the need of development dependencies cluttering the production install. If we do need to add it to the docs, I would suggest adding it under Local Development.

[AramayisO]

@michaelachrisco @fluturecode You can't set NODE_ENV manually. It is set by Node depending on how the process was started. If you run yarn start then NODE_ENV is set to development. If you run yarn build then it is set to production.

[fluturecode]

Moved cross-env to dependencies as part of PR #241, which was merged into dev. Other issue still needs to be addressed.

[michaelachrisco]

@fluturecode Do we think this issue is complete or do we have anything else we need to add at this point?

[fluturecode]

This has been resolved. Pull down the project and run yarn and then yarn start.