-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
The dev server is stuck when using a type alias for the module typesafe-actions #6467
Comments
I have updated the dependencies in the demo repo: diff --git a/package.json b/package.json
index 4981861..8eb25a4 100644
--- a/package.json
+++ b/package.json
@@ -3,17 +3,17 @@
"version": "0.1.0",
"private": true,
"dependencies": {
- "@types/jest": "24.0.6",
- "@types/node": "11.9.4",
- "@types/react": "16.8.4",
+ "@types/jest": "24.0.11",
+ "@types/node": "11.11.3",
+ "@types/react": "16.8.8",
"@types/react-dom": "16.8.2",
"react": "^16.8.2",
"react-dom": "^16.8.2",
"react-redux": "^6.0.1",
- "react-scripts": "2.1.5",
+ "react-scripts": "2.1.8",
"redux": "^4.0.1",
"typesafe-actions": "^3.1.0",
- "typescript": "3.3.3"
+ "typescript": "3.3.3333"
},
"scripts": {
"start": "react-scripts start", The bug is still happening, but now it is getting stuck on |
Any new insights on this? I recently upgraded packages and now experiencing this same "Files successfully emitted, waiting for typecheck results..." message and horridly long build times that tax the proc. The problem occurs with TypeScript 3.4.1 and rolling back to TypeScript 3.3.3333 resolves the issue. It may be related to the new incremental build option..?? |
This issue appears narrow in on the root cause, a conflict between Typescript 3.4.1 and styled-components@4.2.0: |
This issue was just resolved and should be closed. See: microsoft/TypeScript#30663 |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue. |
Hello! First of all, I would like to say that I'm not positive that this issue is caused by
react-scripts
. It might be an issue inbabel-loader
, in the moduletypesafe-actions
, or even intypescript
itself!But I didn't know how to determine where to start, and I think that it's reasonable to open the issue here.
Is this a bug report?
Yes
Did you try recovering your dependencies?
Yes
Which terms did you search for in User Guide?
This issue is not related to anything in the Troubleshooting guide.
Environment
Steps to Reproduce
This issue is related to creating a type alias and using it.
When I develop with
redux
andtypesafe-actions
, I spotted a common pattern:So I decided to abstract it to:
For some reason this does not work. The dev server gets stuck on
Starting the development server...
forever. However, if we inlineDispatcher
it does work as expected.There is no Typescript error, the server is just stuck. I have set up a demo repo; in order to reproduce the bug just do:
$ git clone https://github.com/MeLlamoPablo/dev-server-bug-test-repo $ cd dev-server-bug-test-repo $ yarn $ yarn start
As the repo's
README.md
says, you can find the working version in theworking
branch.Thank you so much for your help!
The text was updated successfully, but these errors were encountered: