build: add Nx

[brandonroberts]

This integrates Nx into the monorepo to manage the build tooling.

• All ng commands are handled by nx
• All existing commands work the same (build/test/e2e)
• Local computation caching is enabled

Closes #342

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/negu3/meme-box/DMZr736ewT4hWGJJkkg96XVAt9nS
✅ Preview: https://meme-box-git-fork-brandonroberts-add-nx-negu3.vercel.app

[negue]

Wooooot!!! awesome 🤩

THANK YOU!!

Did you used any of the existing schematics to convert it to nx or was this all done by hand? :O

[brandonroberts]

Wooooot!!! awesome 🤩

THANK YOU!!

Did you used any of the existing schematics to convert it to nx or was this all done by hand? :O

It was a mix of both 😅. You have multiple projects already, and the existing one to migrate to an Nx workspace currently only supports one project. So I ran

npx add-nx-to-monorepo to add the initial Nx config

Then I took all but one project out of the angular.json and ran

ng add @nrwl/workspace --preserveAngularCLILayout

To fix the Angular config. After that, it was tweaking some of the config files to reference tsconfig.base.json to make sure everything was still working as-is.

If it were a single project Angular CLI project, I would just use

ng add @nrwl/workspace --preserveAngularCLILayout

And remove the newProjectRoot from the angular.json

[brandonroberts]

It did surface some circular dependencies but you probably already knew about those. I did have to turn off automatically building all the dependencies

[negue]

It was a mix of both 😅. You have multiple projects already, and the existing one to migrate to an Nx workspace currently only supports one project. So I ran

npx add-nx-to-monorepo to add the initial Nx config

Then I took all but one project out of the angular.json and ran

ng add @nrwl/workspace --preserveAngularCLILayout

To fix the Angular config. After that, it was tweaking some of the config files to reference tsconfig.base.json to make sure everything was still working as-is.

If it were a single project Angular CLI project, I would just use

ng add @nrwl/workspace --preserveAngularCLILayout

And remove the newProjectRoot from the angular.json

Woah .... this should be a blog post :D or if it already exist - I couldn't find it!

Thank you for the PR! This will really help as base for more awesome nrwl stuff to add.

It did surface some circular dependencies but you probably already knew about those. I did have to turn off automatically building all the dependencies

I saw some but yes those will probably the first things to add now like also adding more lints ... so there is still lots more to go haha

Would you like to be also added to the contributors list on the readme?

[brandonroberts]

Sure I don't mind being added. A blog post is on the list! 😁

[negue]

Sure I don't mind being added.

Awesome! @all-contributors please add @brandonroberts for code

A blog post is on the list! 😁

Hehe, perfect! 😁

[allcontributors]

@negue

I've put up a pull request to add @brandonroberts! 🎉