Cannot find module 'react-scripts/config/paths' about customize-cra HOT 7 CLOSED

hey guys! Has anything made？

from customize-cra.

This issue is difficult to handle because we have no way of knowing the paths location for every custom react-scripts implementation, and there's no way to automatically detect the name of the custom module either. However, since react-app-rewired supports custom scripts versions, I think we should too.

See #103

from customize-cra.

@with-heart Thank you for your reply! I remember react-app-rewired as if we were using .env file to record custom scripts versions, and I thought we could follow suit and use it better with react-app-rewired.

from customize-cra.

That's certainly something you could store in .env and read in config-overrides.js to modify how you override configs, but as far as I'm aware, it's never been something done automatically in react-app-rewired.

As part of #103, I will add a way to inject custom paths to support what you'd like to do here. I'm going to close this issue, so follow along there for updates :)

from customize-cra.

@vegawong You were correct, that should be supported through the REACT_SCRIPTS_VERSION var or the --scripts-version command line option (documented here). That'll be factored into #103.

from customize-cra.

@vegawong Is there a workaround for this use case? I am facing this same issue where I am using custom react-scripts version and getting the same issue.

from customize-cra.

@vegawong Is there a workaround for this use case? I am facing this same issue where I am using custom react-scripts version and getting the same issue.

haha！ I just simply copy the problematic api code into a separate js file to modify and replace the api that is imported directly using from the package.

from customize-cra.