CODEWITHSUNDEEP
node.jstypescriptarchitectureprojects-and-solutions
Max
Max

Reputation: 7080

Typescript NodeJs solution split into multiple projects

I want to develop a typescript nodejs solution split into 3 sub project like a csharp solution split into multiple libraries.

I want that each of them has its own pacakge.json

Obviously, I want from one project to reference another, for example, ui can reference the infrastructure project

In the package.json I found to reference another package using the syntax file::

"dependencies": {
    "infrastrucure": "file:../infrastructure"
  },

The main drawbacks I found:

Cannot read file on <solution root>\tsconfig.json

What I want to know is:

  1. This is the correct approach to split into multiple projects a solution or there are more not considered drawbacks?
  2. Why eslint looking for tsconfig.json into the root folder?

Upvotes: 3

Views: 964

Answers (2)

Max
Max

Reputation: 7080

After a bit of research, I found Rush a monorepos tool by Microsoft.
This tool (for me) is the most similar to a .sln like visual studio and uses the pnpm, the package manager that I already use.

Upvotes: 1

cdimitroulas
cdimitroulas

Reputation: 2539

lerna or yarn workspaces can help you manage a multi-project repository in the way you have described. I'm not sure how to fix your errors without seeing how eslint is setup, but it might be worth looking into these solutions instead of trying to set everything up yourself.

Upvotes: 1

Related Questions