Skip to content
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

chore(repo): add conformance rule for our package.json files #29078

Merged
merged 4 commits into from
Dec 19, 2024

Conversation

JamesHenry
Copy link
Collaborator

No description provided.

Copy link

vercel bot commented Nov 26, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nx-dev ✅ Ready (Inspect) Visit Preview Dec 18, 2024 8:27pm

"@jest/reporters": "^29.4.1",
"@jest/test-result": "^29.4.1",
"@jest/types": "^29.4.1",
"@jest/reporters": "29.7.0",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our jest packages weren't aligned for some reason

@@ -60,5 +60,8 @@
},
"nx-migrations": {
"migrations": "./migrations.json"
},
"publishConfig": {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found by the new rule!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we needed this for provenance... how does rspack have provenance without this?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not for provenance, it's needed because the default access for new scoped package is restricted and so the first time we publish a new package we need this explicit config. Technically after that point we no longer need it anymore, but it doesn't do any harm, just makes its state explicit, and so having this be a rule for all package.json files means we won't run into any issues when new packages are added in future.

Copy link

nx-cloud bot commented Dec 18, 2024

Your CI Pipeline Execution ↗ for commit 0321794 is in progress ⏳

Command Status Duration Result
nx affected --targets=lint,test,build,e2e,e2e-c... ✅ Succeeded 45m 52s View ↗
nx run-many -t check-imports check-commit check... ✅ Succeeded 1m 1s View ↗
nx-cloud record -- nx-cloud conformance:check ✅ Succeeded 1s View ↗
nx-cloud record -- nx format:check --base=1a013... ✅ Succeeded 18s View ↗
nx-cloud record -- nx sync:check ✅ Succeeded 17s View ↗
nx documentation --no-dte ✅ Succeeded 4m 2s View ↗

☁️ Nx Cloud last updated this comment at 2024-12-18 21:12:12 UTC

@nrwl nrwl deleted a comment from nx-cloud bot Dec 18, 2024
@JamesHenry JamesHenry marked this pull request as ready for review December 18, 2024 12:55
@JamesHenry JamesHenry requested review from a team, vsavkin, AgentEnder and jaysoo as code owners December 18, 2024 12:55
@JamesHenry JamesHenry force-pushed the package-json-conformance-rule branch from 059d2f8 to 0321794 Compare December 18, 2024 20:14
@JamesHenry JamesHenry merged commit dfd5014 into master Dec 19, 2024
6 checks passed
@JamesHenry JamesHenry deleted the package-json-conformance-rule branch December 19, 2024 12:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants