-
Notifications
You must be signed in to change notification settings - Fork 90
chore: watch mode #141
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: watch mode #141
Conversation
AriPerkkio
commented
Jul 15, 2024
- Fixes Watch mode for development #128
|
There's still an issue on I've tried all kinds of combinations of |
ce6e813
to
4ca8a5b
Compare
You may wish to test your locally-modified copy of TutorialKit against another package that is using it. For pnpm, after building TutorialKit, you can use [`pnpm.overrides`](https://pnpm.io/package_json#pnpmoverrides). Please note that `pnpm.overrides` must be specified in the root `package.json` and you must first list the package as a dependency in the root `package.json`: | ||
|
||
```json | ||
{ | ||
"pnpm": { | ||
"overrides": { | ||
"@tutorialkit/astro": "file:../tutorialkit/packages/astro", | ||
"@tutorialkit/components-react": "file:../tutorialkit/packages/components/react", | ||
"@tutorialkit/runtime": "file:../tutorialkit/packages/runtime", | ||
"@tutorialkit/theme": "file:../tutorialkit/packages/theme", | ||
"@tutorialkit/types": "file:../tutorialkit/packages/types" | ||
} | ||
} | ||
} |
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.
This works somewhat ok but is quite far from ideal. Due to file:
usage, the project must re-run pnpm install
after TutorialKit packages have updated.
Using link:
would make changes automatically visible, but I was unable to solve issue where TutorialKit's dependencies brought multiple copies of React into the runtime and caused hooks to fail. With webpack this could be solved using resolve.alias
but it just doesn't work with Vite.
a39abe8
to
f86dc11
Compare
f86dc11
to
b32ffdc
Compare
Adding I tried to force it from the |
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.
Looking good! I really like the improvement and normalization on the build script.
I would reduce a bit on the number of watch processes started though, I left some comments here and there to clarify where I think they could be removed.
.github/commit-convention.md
Outdated
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.
I wonder if we should use the same convention than for the rest of StackBlitz's repos. Curious to hear your thoughts @d3lm on the topic.
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.
(FYI this is from Vitest repo)
Co-authored-by: Jòan <Nemikolh@users.noreply.github.com>
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.
Let's goooo!!!