You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm always frustrated when my files are changed by react-scripts. I added some compileroptions.paths to tsconfig.json then I npm start. Then the error pops up FOR ONLY A FEW SECONDS. I did not notice it at the first three times.
compileroptions.paths must not be set (aliased imports are not supported)
Then the compileroptions.paths is removed. More frustratingly, it cannot be undone.
Describe the solution you'd like
Stop changing the file, or at least show in console what is going to be changed.
Do not clear the console when there's an error.
Describe alternatives you've considered
show in console what is going to be changed.
show the error again after console is cleared.
Additional context
I checked #9406 and #10882. They are discribing diffrent aspect of related issue. What I emphasize is the user(programmer) experience.
The text was updated successfully, but these errors were encountered:
Is your proposal related to a problem?
I'm always frustrated when my files are changed by
react-scripts
. I added somecompileroptions.paths
totsconfig.json
then Inpm start
. Then the error pops up FOR ONLY A FEW SECONDS. I did not notice it at the first three times.Describe the solution you'd like
Describe alternatives you've considered
Additional context
I checked #9406 and #10882. They are discribing diffrent aspect of related issue. What I emphasize is the user(programmer) experience.
The text was updated successfully, but these errors were encountered: