Replies: 10 comments 10 replies
-
I'm assuming this is a typo where |
Beta Was this translation helpful? Give feedback.
-
Thanks for sharing detailed Roadmap. Angular 12 with Webpack 5 support will be part of Nx 13. |
Beta Was this translation helpful? Give feedback.
-
Very exciting changes :) I hope you will consider experimental support for Webpack 5 sooner than October if possible, even if it is not officially supported yet, and even if the "shiny new features" like module federation, etc, are not usable yet. I have already started to run into issues with Webpack 4 like:
Personally I can work around these issues, but they are difficult to debug, and I think these kinds of issues may affect more people and projects in the coming months, since:
Nx is fantastic tool, thank you for maintaining this system :) |
Beta Was this translation helpful? Give feedback.
-
@vsavkin - I understand that there's a TON of work that goes into a major version upgrade like this. With that said, why do you suppose it can't be done until October? Is there anything we, as part of the community, can do to help expedite it? Angular 12 came out today, btw! Now Webpack 5 is supported in production and not just considered experimental. One more feature request: with ng 12 and Webpack 5, module federation and micro-frontend patterns are finally accessible. |
Beta Was this translation helpful? Give feedback.
-
Could support for BlitzJS be introduced for NX 13? Thanks |
Beta Was this translation helpful? Give feedback.
-
webpack 5 support is coming! |
Beta Was this translation helpful? Give feedback.
-
Cypress: Could you consider including Cypress Component Testing too? Fantastic work for the last few versions (since I have started using Nx). It has been a life-changer! |
Beta Was this translation helpful? Give feedback.
-
Is Vue support coming sometime in the future? Would like to try this out on a Vue monorepo, maybe even do custom commands for Go backends |
Beta Was this translation helpful? Give feedback.
-
@vsavkin When are we expecting this drop? Is there a status page somewhere we can monitor? |
Beta Was this translation helpful? Give feedback.
-
@vsavkin Has this landed in NX 13, or is it planned for some minor version in the future?
|
Beta Was this translation helpful? Give feedback.
-
Read this post to learn about what is new in Nx 12.
Core
Supporting Large Workspaces
In Nx 12, we have updated our code change analysis and hashing algorithms to make sure that only relevant parts of
workspace.json
get into the hash. Now changing the global config file no longer invalidates the hash of every project or marks everything as affected.In Nx 13, we will allow you to split your configuration into multiple files. Every project can have
nx-project.json
with its config in its directory. With this workspace.json will become a lot smaller which will simplify rebasing.Deps Between Targets
Nx will allow you to specify how targets depend on each other. You will be able to express things like "To test Project A, I need to build all the deps of Project A first". With this, when you invoke
nx test a
, Nx will run the necessary build tasks automatically (most likely retrieving them from the cache).More Work on Plugins Adding/Removing Edges
In Nx 12, we provided a way for a plugin to be invoked in the dep graph creation process. Now Nx can analyze Java/Go/Rust/etc similar to JS/TS. We are working on examples, docs, blog posts showing how to do it.
Incremental Builds Are Recommended Way for Mid-Size/Large Apps
Currently, it’s a good option only for large apps. For everything else the costs outweigh the benefits. We are working on a series of improvements to make this a good option for an application of any size. Some of the improvements have already been released (e.g., optimizing cache restoration, which can a problem on Windows due to slow IO), some are going to be released in 12.1 (e.g., Deps Between Targets), and some will be released shortly after (e.g., testing and linting taking advantage of incremental builds).
React & Next.js & Gatsby
We’ve been putting a lot of effort into making Nx the best tool for building any React application. Nx 12 came with a tonne of bug fixes and small improvements. We released a command migrating any monorepo to Nx in 30 seconds. We also released a command migrating existing CRA projects to Nx. We are continuing this work.
In addition, we are planning to:
Angular
We are planning to:
Storybook
We are planning to:
Nx Console (VSCode Plugin)
We have several engs now working on Nx Console, so expect a lot of improvements.
Some highlights:
Cypress/Jest/ESLint
We’ll update the versions of Jest, Cypress, ESLint, Storybook. We are also working on drastically speeding up tests and lints for large workspaces by utilizing buildable libs.
Nx.Dev is Rewritten in Next.js
The docs site is being rewritten in Next.js. As a result, the process of publishing the docs is going to be streamlined.
Support for Distributed Command Execution
Nx will provide affordances for distributed command execution, where
nx affected ...
ornx run-many ...
or evennx build myapp
will be able to run on multiple agents. Nx Cloud is going to use those affordance to provide config-free distribute command execution, but you can also build your own.Nx 13 will be released in October 2021.
Beta Was this translation helpful? Give feedback.
All reactions