-
Notifications
You must be signed in to change notification settings - Fork 69
feat: rename API package to @netlify/api
#6247
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 pull request adds or modifies JavaScript ( |
This pull request adds or modifies JavaScript ( |
This pull request adds or modifies JavaScript ( |
Is there a plan for how the package name swap will be done? If we want to use Do we know how to instruct various dependency bumper (dependabot, renovate, etc) to swap package names appropriately so those could automatically do package name swap? For packages we control doing this manually I think is fine even if a bit busy work, but for external consumers this whole thing might cause confusion and potentially problems for them to deal with? For example for renovate https://docs.renovatebot.com/configuration-options/#replacementname and there is example for when Vercel rebranded from Now ( https://github.com/renovatebot/renovate/blob/866cdb391b78f368ea7c6c9baf62e36343fce2e6/lib/data/replacements.json#L767-L778 ), but I'm not very familiar if there is something potentially more automatic that could just apply to all dependency managers like that ---edit |
@pieh My plan is to keep exporting the same API interface from the new We'll cut a new major and in the change log explain that they should change to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This pull request adds or modifies JavaScript ( |
Summary
Starts publishing the API client as
@netlify/api
so that we can repurpose thenetlify
package for the CLI.