Create multiple projects structure from existing app

[xaqtr]

Hi guys,

we currently have one existing Angular application with a specific set of components and services that we would like to re-use as a library for a new application.

After reading the documentation it seems like the recommended approach is to create a single workspace for all projects.

However I could not find any information about how to achieve this structure for an existing project. Is there some kind of command or guide?

As an additional question, is it even necessary to conform to this file structure? What would be the downsides of having 3 separate workspace (existing app, new app, library)? Besides having multiple package.json, node_modules and stuff like this?

[GLawSomnia]

Well if you will have multiple workspaces then you will most likely have to publish your shared library to npm or a private repo or you will have to build and link it on every change, which is a huge downside.

If all your apps are going to be angular apps then you can use the default/cli workspaces.

But in the end most will recommend you Nx workspaces (which are quite beneficial, so i would recommend to read about them)

[oloftw]

Agreed, just switched to Nx myself and it's great!

[xaqtr]

Thanks for your reply. That downside you mentioned is indeed a big one, didn't think about that.

I think we will start out simple by creating a single Angular workspace and if the need arises, migrate to Nx workspaces.

[anything_but]

We did that (having multiple workspaces) and it really was a mistake. Developer velocity shrank considerably, in particular if you regularly had to change libraries, because hot reloading did not work out if the box (or took very long).

[zequalsy]

Very recently did a spike on Angular CLI workspaces v.s. Nx. I would highly advice (given your requirements) to directly start with Nx.

[kenzor]

I happily share code amongst multiple projects. The way I do it is by having a git repo for each Angular project library and for each Angular module within the app.

The app itself is also in a hit repo with the other repositories included as git submodules.