-
Notifications
You must be signed in to change notification settings - Fork 71
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
feat: rename tutorialkit
to @tutorialkit/cli
#153
Conversation
|
a27dbe0
to
055b157
Compare
This package used to exist, I think we might have cleaned the alpha versions that we had published for testing. Hopefully that won't be a problem. |
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.
Looks good! Love the cleanup as well 🤗
I think this is actually not a breaking change as CLI packages are not installed by end-users. I'll resolve the conflicts and then we can merged this. |
Yeah I agree, let's move forward with this PR 👍 |
Co-authored-by: Jòan <Nemikolh@users.noreply.github.com>
54931d7
to
fdc8f42
Compare
tutorialkit
to @tutorialkit/cli
tutorialkit
to @tutorialkit/cli
tutorialkit
to@tutorialkit/cli
CONTRIBUTING.md
about package naming convention. This is mostly related to development time communication practices and doesn't affect end users.tutorialkit-vscode
totutorialkit
. Removes work-around from build script that was used to do this renaming right before publishing. This name is already used by the published extension.BREAKING CHANGES:
tutorialkit
npm package is now unused. We should probably deprecate that from npm? Or just leave it as is.@tutorialkit/cli
. This package does not yet exist in npm. I'm not sure if publishing this package will work without any permission settings. Do we need to add https://www.npmjs.com/~stackblitz-devops there some how?