-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: migrate to nx #30267
Comments
Hotell
changed the title
[Feature]: migrate to nx for task orchestration
[Feature]: migrate to nx
Jan 9, 2024
2 tasks
This was referenced Jul 3, 2024
Merged
This was referenced Jul 29, 2024
feat(scripts-package-manager): dont run git hooks on CI, notify user to run install if needed
#32169
Merged
This was referenced Aug 21, 2024
This was referenced Aug 28, 2024
This was referenced Sep 10, 2024
This was referenced Oct 3, 2024
This was referenced Oct 11, 2024
This was referenced Oct 22, 2024
All tasks have been completed ! 🚀
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Library
whole monorepo
Describe the feature that you would like added
nx suites well for our needs as a robust core building blog for best possible mix of great DX, unified tooling, excellent task orchestrator etc under "1 package". Recently nx also added release tool and support for other technologies beyond JS ecosystem which matches with what we would like have in our arsenal ( with more JS tooling shifting towards other languages ).
We already have nx in repo for quite some time, which was used only for generators and various codemods automations.
in recent months we did various preparations for actual nx migration
project.json
to every projectGoing forward we wanna completely move to nx coherent DX in all areas.
Have you discussed this feature with our team
v-build
Additional context
No response
Tasks
@fluentui
scope / chore: normalize project names in whole repo #31893build:react-with-umd
task for v8 packages that ship UMD to production(npm registry) #32031yarn start
experience / feat(scripts-executors): implement newyarn start
experience #32108sourceAnalyzer
in order to build dependency graph instead of relying on static package.json dependency definitions / chore(nx): enable analyzeSourceFiles in order to build dependency graph based on source files instead statically defined package.json dependencies #32359build
executord.ts
emit feat(workspace-plugin): addgenerateApi
functionality/flag to build executor #32976generate-api
executor / feat(workspace-plugin): implement generate-api executor #32418type-check
executor / feat(workspace-plugin): implement type-check executor #32370clean
executor / feat(workspace-plugin): implement clean executor #32401verify-packaging
executor / feat(workspace-plugin): implement verify-packaging executor #32403lint
- we will use inferred lint task created by@nx/eslint/plugin
test
- we will use inferred lint task created by@nx/jest/plugin
bundle-size
- keep as is (usingmonosize
cli directly )e2e
- keep as is ( usingcypress
cli directly )storybook
- keep as is ( usingstorybook
cli directly )test-ssr
- keep as is ( usingtest-ssr
cli directly )code-style
- replace withformat
target ( will usenx format
orprettier
CLI directly ) / chore(scripts/*): replace just-scripts and npm script aliases with nx #32371Priority
None
Related Issues
NX issues
--parallel
argument doesn't override env variableNX_PARALLEL
nrwl/nx#26903show project
: renders duplicate target when using inferred task frompackage.json#scripts
nrwl/nx#27143NX Features (missing/requested)
Issues that can be closed after this Epic is implemented:
info
command if untracked files are present #26147lage
tov1.10.0
#31710The text was updated successfully, but these errors were encountered: