Automating for Speed and Quality with the Nx Devkit - Juri Strumpflohner - Nx Conf 2021

[@jornejongsma]

22:30 "Now let me also use skip nx cache...", Pretty critical!

[@avimehenwal]

I was building something similar like what NX generator does using old tool called yeoman. Glad I found this tutorial. NX is great, now I am using it for all of my projects "at scale". great job people @Narwhal, kudos

[@jackbarry3893]

Getting a POC set up to try out Nx, this answered a lot of questions I had about getting started with Executors/Generators/Plugins. Thanks!

[@moatorres]

Is it just me or everyone that has at some point created a `cli-deps` symlinked-local-library to speed up things, is absolutely mindblown by Nx?

[@jandrorojas6714]

can someone please explain to me how on earth can I use a generator from an executor and vice versa?

[@nxdevtools]

Usually, those are two different things. Generators scaffold new code, while executors are more sophisticated wrappers around custom node scripts to build/run/test/... your projects. Here are some potentially useful links: - nx.dev/recipes/generators - nx.dev/recipes/executors

[@jandrorojas6714]

@@nxdevtools thanks for the reply. I get that conceptually they are two different things. However, I don’t get why they can’t be executed in conjunction just like a regular angular schematics. For example, I’d like to set up (generate) some temporary files, serve (execute) the app, and cleanup the previously generated temporary files (most likely another generator). One command that does everything. Is that possible? If not, I might have to go back to regular angular schematics (which is a shame since everything else with no is top notch)

[@adamzugasti]

Are there example plugins for iOS development?

[@BrianVanderbusch]

why would i keep project configuration such as implicitDependencies in a separate file at the root of repo instead having it in the project.json of the project? Seems like a bad idea to split this configuration out as it makes it harder to debug or pickup for new contributors.

[@BrianVanderbusch]

I also notice the docs for nx as of latest version don't have "projects" as a key for the nx.json, so maybe this has been resolved?

[@additionaddict5524]

I don’t like the implicitDependacies hack. Coming down the line are devkit apis that calculate the project dependencies and this pollutes the output from this. I prefer nx:run-commands and sticking nx build plug-in as first entry in build > options > commands array.

[@nxdevtools]

This is a talk from 2021. That hack is no more need 😃: nx.dev/plugin-features/create-your-own-plugin#local-workspace-plugins There are also some videos in our YT that show local generators which use that new approach