🌊 #Nx 17 standardizes generator options and adds the nameAndDirectoryFormat and projectNameAndRootFormat options accepting:
- as-provided: generates files relative to the current working directory and ignores the project option
- derived: uses the project option generates files relative to the workspace root directory
The `project` and `flat` options are deprecated in favor of the `directory` option and --project-name-and-root-format=as-provided
🌊 #Nx 17.0 adds the `NX_PARALLEL` environment variable to ease reusing Nx commands between different environments https://nx.dev/reference/environment-variables#environment-variables
As an example, let' say we have defined a `ci` script in `package.json` that runs the command `nx run-many --targets=build,lint,test`
🌊 #Nx 17.0 removes the deprecated `defaultCollection` setting from `nx.json`. This means that `nx generate library my-library` now prompts us to select from alll packages that have a `library` generator.
Alternatively, we specify the package in the command: `nx generate @nx/angular:library my-library`
🌊 #Nx 17.0 adds the `nxCloudUrl` setting to `nx.json`. Useful for Nx Cloud Enterprise https://nx.dev/nx-api/devkit/documents/NxJsonConfiguration#nxcloudurl
inmedica susijunge su kardiolita, mano gyd. istaigos ir seimos gyd. nebera inmedica systemoje,o kardiolitoj dar nera 🤬🤬🤬 #NX
Here is a .NET Nx workspace set up using nx-dotnet, #Nx, and #GitHub Actions https://github.com/LayZeeDK/github-actions-nx-dotnet
I'm excited about the @nx/dependency-checks ESLint rule introduced in #Nx 16.4. I submitted bugs that were patched in Nx 16.5 while writing this article.
Use it as a replacement for `updateBuildableProjectDepsInPackageJson` when maintaining peer dependencies for buildable or publishable Nx libraries.
🌊 #Nx deprecation ⚠️
The `nx workspace-lint` command is deprecated in Nx versions 15 and 16 where the command is a no-op. The command is removed in Nx 17.
1. Remove usage of the `nx workspace-lint` command from your scripts and CI pipelines.
2. Use standalone project.json configurations, not workspace.json or angular.json.
3. Ensuring that Nx package versions are in sync is supported by manually inspecting the output of the `nx report` command.
🌊 #Nx deprecations ⚠️
- Nx CLI support for workspace.json and angular.json is deprecated
- Nx Console no longer supports angular.json
Still using workspace.json or angular.json? Run `nx g @nx/workspace:fix-configuration` and then delete workspace.json or angular.json
Still using Angular CLI? Run `nx init` to add Nx
I contributed examples to the #Nx documentation for running tasks based on Nx project tags using the `nx run-many` command https://nx.dev/packages/nx/documents/run-many#examples. Thanks to fellow Nx Champion Jay Bell for support in figuring this out and thanks to @agentender for helping with documentation commits.
#TIL The `--only-failed` option for the `nx affected` and `nx run-many` commands was removed back in #Nx version 13.3. Here's why https://github.com/nrwl/nx/issues/7847#issuecomment-1024468887
Introducing Nx Ecosystem CI
New #Nx article on enforcing architectural boundaries by Nx Champion Nacho Vazquez Calleja
#Parasolid history its begun 70 years ago! What??? What WTF? this statement is wrong and this isn't the year but the version :) Romulus was released 1978 and its impossible, maybe studies begun years before #Unigraphics #NX #CAD Parasolid the core of many CADs and also of #Plasticity
✍️ Stop using the defaultProject #Nx CLI setting and start using NX_DEFAULT_PROJECT
👀 Introducing #Nx Champions https://blog.nrwl.io/introducing-the-nx-champions-program-6164c6f15dad
Nx 16 [“smart, fast and extensible build system”]
#Nx 15.7 introduced first-class #Deno support. Now, with Nx 16.0, the @nx/deno preset has been added, an `oak` option has been added for the `framework` option, and edge functions have first-class support with the @nx/netlify and @nx/aws-lamda packages. Deno Deploy is also supported https://blog.nrwl.io/nx-16-is-here-69584ec87053#f71b
#Nx 16 was released on Friday, April 28th. Packages that previously had the @nrwl npm scope now have the @nx npm scope. For example @nx/angular, @nx/cypress, and @nx/react. Of course, this is handled automatically by Nx migrations when running the `nx migrate latest` command. For compatibility, the `@nrwl/*` packages are available in v16.x but >=17 will only be published using the @nx npm scope https://blog.nrwl.io/nx-16-is-here-69584ec87053#8e44
Big shakeup in the #TestAndMeasurement space!
It will be interesting to see how #LabVIEW evolves...
To #Linux users, who often complain about the lack of commercial #CAD software, there are some as we know like #Varicad and others but a new one arrives in April and one of the best applications I've had the opportunity to use go and buy it, trust me! It's #Plasticity and has the same engine of #Siemens #NX (Parasolid) and works truly very well.
Images below are from Siemens Web.
Finally the official Nx console for Jetbrains IDE has arrived:
Just in time for my first Nx project 😎
How do you generate a library with many tags in NX?
This command: `nx g @nrwl/angular:library todos --tags=tag1,tag2`
generates these tags in the project.json:
`"tags": ["tag1 tag2"]`
I would expect two strings in the tags array.
From my package.json:
I contributed an update to the #Nx docs. #Angular 15.1 version compatibility is now listed.
Really must give #nx a go, been on my must try list for months now .... https://dev.to/zchapple/modernization-with-module-federation-nx-and-react-4kj5
Green Book - Eine besondere Freundschaft ... ist ein sehr besonderer Film. Empfehlung!
At work I own the entire architecture of and write the code for an application with two features thus far:
- search and discovery in cross-organizational data
- scoring value models (evaluating subjective data to identify trends in a particular subject area)
I have #NestJs, #React, and a few other #TypeScript projects in a monorepo managed with #Nx. I also spend a fair amount of time in Python for configuring ETLs and utilizing the amazing tools written by my data scientist colleagues.
I've just asked my first question on #StackOverflow in what feels like forever! If you're a #nrwl #nx pro, could you help me here? I have a workaround which is running 2 separate commands but feels like nx should know what to do here properly
Aaaaand now I'm building an #Nx dependency graph plugin to create a dependency graph inside of a gigantic Flow monorepo with a bespoke module system.
It's absolutely bonkers how flexible and extensible https://nx.dev is.
One cool thing about this is that I'll be able to just delete the plugin once we make the migration from Flow to #typescript, but improved monorepo tools are not blocked on a TypeScript migration.
Hacking away at a custom #nx monorepo configuration and I continue to be blown away by how powerful it is.
I now have #nx bolted onto a gigantic pre-existing Flow monorepo with auto-generated `project.json` files, providing CLI access to every project's targets.
Next thing is to figure out how to get the dependency tree working so we can use `nx affected` to streamline CI runs.
Hoping this might take my #AzureDevOps CI/CD pipelines in an interesting direction.
Definitely something to keep an eye on.
Announcement here: https://github.com/dotnet/announcements/issues/241
@vertigo Gosh darnit this is the second reference to this piece I've heard in the last week. It was put up during some podcast or something as one of the most complicated prog rock pieces ever done - primarily due to the constantly changing time signature in the intro and of course Hackett's guitar solo.
I just put it on in the background as I'm typing. Thanks for the reminder. :). #nx
@inlovewithpda I HAVE 3 OF THESE!
Ahem. I mean, yes, I know these units. See https://planet-geek.com/2017/11/24/vintagehandhelds/sharp-zaurus-sl-5500-linux-pda/ - I believe one of my 5600's still has the original rom on it, I may be able to image it, let me know. #nx