Open ghost opened 5 years ago
Upon further research it seems this issue may be reoccurring in CRA: facebook/create-react-app#5003.
i'm having the same issue. I've installed recently node 10 and since then...
I have switched to CRA 2.1 which added TypeScript support and came out a few days back, that may be an option for you as well, @dnicoara-psft. Migrating from create-react-app-typescript to Create React App
Just an FYI, obviously this issue still stands.
@tomashubelbauermicrosoft How is your experience so far? I am facing a lot of linting related issues in CRA 2.1
.
I have not noticed anything of that sort yet, however it's been only a few days. Can you give me a few examples of what is subpar in the CRA version as opposed to the CRA-TS one in terms of linting?
Another motivator for the bump: https://www.npmjs.com/advisories/725
This is a high warning, needs fixing!!
Alternatively, @wmonk please consider marking the repository as archived, if it is no longer maintained. If it isn't, that's absolutely fine, but it should be indicated so that people know not to use it for new stuff.
Same problem here, any news for a fix?
The project has been deprecated and was archived at some point (it seems to have been un-archived to update the readme and then not re-archived again). In any case, don't expect this package to be updated @MikaelStenstrand.
The transition to Create React App was relatively smooth in a project I'm working on, so I recommend making the transition to that project instead. The guide posted in an earlier comment was of great help. Good luck! 😄
I am running into an issue in CRA TS which seems to be caused by an outdated
webpack-dev-server
dependency. The issue is nodejs/node#21665 and it used to occur in CRA too as it was also using an outdated version of the dependency and has since updated it. CRA TS is still using an affected version and the issue reproduces for me in CRA TS:create-react-app repro --scripts-version=react-scripts-ts
cd repro
.env
file and placeHTTPS=true
in itnpm start
I believe the fix would be to update
webpack-dev-server
the same way. For me this happens on Windows but it should happen under the same conditions described in the linked issue for anyone.