You can try ctrl+shift+p and searching for restart typescript server. That's much faster than restarting VSCode. It's frustrating that you have to do this sometimes, but I do find that it occurs more often when I have plugins that are interfering.
So you can also try:
1) Making sure you don't have the deprecated version of the TsLint plugin
2) removing all of your plugins if that doesn't work
3) try running Madge to see if you have a circular dependency
Hey @cubiclebuddha
, how to you manage the context to avoid circular dependencies.
For example:
The way we generally do, I have context declared and provided in app.tsx. The app.tsx have dependency of let say page-one.tsx and I want to consume the context in page-one.tsx. (obviously in such scenario passing the props itself enough but consider a deep hierarchy that needs context) Such scenarios will create circular dependency. Do you suggest declaring the context variable in altogether separate file?
Also, I want to test some good production application(not library) built using CRA typescript with mine. So that I can compare and better understand. Do you have any such opensource application in mind?
If I have a circular dependency between a.ts and b.ts, I pull out the shared code into c.ts and use that in a and b. It shouldn’t matter if it’s function or a function component because it’s all just references.
And sadly, no I don’t know of a good example of a create React app in TypeScript. I’m only just beginning on React myself. Sadly I was stuck in Angular 1 for a long time. 🤮
Haha Welcome buddy. And we are beginner with TypeScript in React.
I tried Madge and solved all circular dependencies but still there is no significant improvement with that. So not sure if there is something else to check or it's just the way it will be.
Thanks :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You can try ctrl+shift+p and searching for restart typescript server. That's much faster than restarting VSCode. It's frustrating that you have to do this sometimes, but I do find that it occurs more often when I have plugins that are interfering.
So you can also try:
1) Making sure you don't have the deprecated version of the TsLint plugin
2) removing all of your plugins if that doesn't work
3) try running Madge to see if you have a circular dependency
I think, I am good with 1 and 2. I should give a try to Madge.
Hey @cubiclebuddha , how to you manage the context to avoid circular dependencies.
For example:
The way we generally do, I have context declared and provided in
app.tsx
. Theapp.tsx
have dependency of let saypage-one.tsx
and I want to consume the context inpage-one.tsx
. (obviously in such scenario passing theprops
itself enough but consider a deep hierarchy that needs context) Such scenarios will create circular dependency. Do you suggest declaring the context variable in altogether separate file?Also, I want to test some good production application(not library) built using CRA typescript with mine. So that I can compare and better understand. Do you have any such opensource application in mind?
If I have a circular dependency between a.ts and b.ts, I pull out the shared code into c.ts and use that in a and b. It shouldn’t matter if it’s function or a function component because it’s all just references.
And sadly, no I don’t know of a good example of a create React app in TypeScript. I’m only just beginning on React myself. Sadly I was stuck in Angular 1 for a long time. 🤮
Haha Welcome buddy. And we are beginner with TypeScript in React.
I tried Madge and solved all circular dependencies but still there is no significant improvement with that. So not sure if there is something else to check or it's just the way it will be.
Thanks :)