-
Notifications
You must be signed in to change notification settings - Fork 41
v3 #634
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
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 22711f5 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
jsrepo
@jsrepo/mcp
@jsrepo/migrate
@jsrepo/transform-biome
@jsrepo/transform-javascript
@jsrepo/transform-prettier
commit: |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Aidan Bleser <aidanbleser35@gmail.com>
Co-authored-by: aidanbleser35 <aidanbleser35@gmail.com> Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is jsrepo v3 :)
Docs can be found at: https://v3.jsrepo.dev
Please add any comments to this discussion #629
For anyone moving from v2 you can checkout the Migration Guide or just run:
Before this merges...
nextbranch ->mainv3.jsrepo.dev->jsrepo.devv2.jsrepo.devjsrepo.devregistry:shouldn't need to be prefixed withregistry:in the paths object--no-cacheoptionNeed a solution for versioning registries now that we are using a js based config. Kinda shitty but we need our own version of changesets. I think this is a good opportunity for innovation towards something that works specifically well for registries though.Actually I think we can just use the version from the package json since most of the time all registries will just have the same version.tsor.mtsconfig based on package.jsontypesetting@jsrepo/mcpdoesn't work with npxmetaon registry itemsFixes #626
Fixes #628