You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for showing interest in using TutorialKit! We are currently planning to do a 1.0 release and we're excited to share a list of the changes that we are intending to make before the release.
Planned Changes
🚨 Renaming tutorialkit to @tutorialkit/cli. So we can use that name for the vscode extension and also because the npm create tutorial command is the recommended way to create a new tutorial.
Hey there!
Thanks for showing interest in using TutorialKit! We are currently planning to do a 1.0 release and we're excited to share a list of the changes that we are intending to make before the release.
Planned Changes
tutorialkit
to@tutorialkit/cli
. So we can use that name for the vscode extension and also because thenpm create tutorial
command is the recommended way to create a new tutorial.tutorialkit
to@tutorialkit/cli
#153@tutorialkit/components-react
to@tutorialkit/react
and move it fromcomponents/react
toreact
. Simpler name and descriptive enough.@tutorialkit/components-react
to@tutorialkit/react
#155src/content/config.ts
to import the full schema from@tutorialkit/types
.contentSchema
#156@tutorialkit/theme
.content.inline
tutorialkit:store
tutorialkit:core
provide low level access to webcontainer and is to be used only as a last resortcreate-tutorial
depend on"@tutorialkit/cli": "latest"
and release a fire and forget version.create-tutorial
releasing #146.vscode/settings.json
.settings.json
#173Nice to have, some post 1.0.0 launch:
TutorialStore
classThe text was updated successfully, but these errors were encountered: