I wish you guys would post up github repos related to these videos. Docs are super hard to follow and the generator didn't work with some of my custom set up...
Amazing, looks really simpler and better, hope better DX. One question is about TS noemit vs lint, I need to check before commit this TS because is out of scope of linter. Does NX has some tool to cache this TS work that in a big codebase project could take some time and just for a simple commit?. Thanks!
for the plugins we use at nx, we'll set up a "lint" script to run eslint, but as far as TS goes, we actually tend to just set things up to build (so emit is on) - and use this passing as a signal that TS is happy as a type-checker
Typically I'm specifical of the `fixes` myself - I certainly wouldn't want for them to auto--run on save. For nx, any options are passed to eslint, so you can run `nx lint my-project --fix` and that will attempt to fix the fixable errors for you. My advice though: drop a quick git commit before running that badboy!
not yet - but iirc biomejs is the reason we recently renamed the @nx/linter plugin to @nx/eslint. I don't know if there's a first-party biomejs plugin in the near future, but especially with project crystal now that should be pretty simple to setup!
ehh mostly! I don't _believe_ there's a built-in cascade to tsconfigs like we saw, so if you want to extend other tsconfigs, you need to do so manually with that extends property.
Switching over now. Thanks for the demo.
Love it!
great video
I wish you guys would post up github repos related to these videos. Docs are super hard to follow and the generator didn't work with some of my custom set up...
How do you integrate prettier into the nx eslint config for automatic formatting on save?
I wouldn't use eslint for formatting personally - I just like prettier for this!
Amazing, looks really simpler and better, hope better DX.
One question is about TS noemit vs lint, I need to check before commit this TS because is out of scope of linter. Does NX has some tool to cache this TS work that in a big codebase project could take some time and just for a simple commit?.
Thanks!
for the plugins we use at nx, we'll set up a "lint" script to run eslint, but as far as TS goes, we actually tend to just set things up to build (so emit is on) - and use this passing as a signal that TS is happy as a type-checker
Any tools plugins to autofix some of the fixable errors using nx lint?
Typically I'm specifical of the `fixes` myself - I certainly wouldn't want for them to auto--run on save. For nx, any options are passed to eslint, so you can run `nx lint my-project --fix` and that will attempt to fix the fixable errors for you. My advice though: drop a quick git commit before running that badboy!
Any support for biomejs, I'm tired of eslint configuration...
not yet - but iirc biomejs is the reason we recently renamed the @nx/linter plugin to @nx/eslint. I don't know if there's a first-party biomejs plugin in the near future, but especially with project crystal now that should be pretty simple to setup!
What about the extends option in the tsconfig? Does it work the same as in the eslint config?
ehh mostly! I don't _believe_ there's a built-in cascade to tsconfigs like we saw, so if you want to extend other tsconfigs, you need to do so manually with that extends property.