Ok I read it, doesn't really answer my question and just leads me to believe this is more of an IDE question than Nx question. If I am using Project References w/ Workspaces, how does my IDE know where to import my stuff from? 1/x - ThreadSky

About ThreadSky

jaycooperbell.dev • 29 days ago

Ok I read it, doesn't really answer my question and just leads me to believe this is more of an IDE question than Nx question.

If I am using Project References w/ Workspaces, how does my IDE know where to import my stuff from?
1/x

Comments

jaycooperbell.dev•29 days ago

Lets say I generate a new lib `mylib` and add a function `myfunc`, I know Nx will setup the root tsconfig and such, but if I go to an existing lib and start typing `myfu` how does the IDE know where to import that from? Before it knew due to aliases, but until nx sync is run, the ref does not exist.

mhartington.io•29 days ago

Ahh, so that's part of "workspaces". When you set the workspace in the package.json, npm will hoist any packages in there to the root level node_module. From there it's just node's module resolution.

Project refs just tell the IDE about the Types. Workspaces tell the IDE where things are

jaycooperbell.dev•29 days ago

Ah ok, I think I just need to play with it then. I haven't used workspaces before so this is introducing multiple topics to me. Trying to delineate between what is what.

mhartington.io•29 days ago

Yeah, they go hand in hand but do different things. You _could_ use one without the other, but then you dont get the full experience

jaycooperbell.dev•29 days ago

Makes perfect sense, can't wait to try it! (Once, we can use it with @angular.dev...)

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply