Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On deleting compileroptions.paths #11310

Open
PabloLION opened this issue Aug 16, 2021 · 0 comments
Open

On deleting compileroptions.paths #11310

PabloLION opened this issue Aug 16, 2021 · 0 comments

Comments

@PabloLION
Copy link

Is your proposal related to a problem?

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

  1. Stop changing the file, or at least show in console what is going to be changed.
  2. Do not clear the console when there's an error.

Describe alternatives you've considered

  1. show in console what is going to be changed.
  2. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant