b8a6f9b8b8
* feat: support pre render ssr * chore: modify global to window * chore: deal with lint * chore: add type * chore: remove console * feat: get assets * chore: modify concat * chore: add changeset * fix: fix lint warning |
||
|---|---|---|
| .. | ||
| README.md | ||
| config.json | ||
| nice-vans-float.md | ||
| popular-shirts-explain.md | ||
| proud-buckets-beg.md | ||
README.md
Changesets
Hello and welcome! This folder has been automatically generated by @changesets/cli, a build tool that works
with multi-package repos, or single-package repos to help you version and publish your code. You can
find the full documentation for it in our repository
We have a quick list of common questions to get you started engaging with this project in our documentation
Add A Changeset
Read the documentation for more detail.
Publish Snapshot Version
NOTE: It is useful for you to release a version to test your package on your current branch.
Run the following command to publish the snapshot version:
$ npm run release:snapshot
After that, you don't need to commit the change to the branch.
Publish Beta Version
NOTE: Recommend you to publish a beta version on a new branch(such as
release-beta) which is checked out from therelease*branch.
Run the following command to publish the beta version:
$ npm run release:beta
Then, we need to commit the changes to the branch.
For more detail, please see this documentation.
Publish Latest Version
GitHub bot will automatically create a PR to update the latest versions for the released package.
What we need to do is to merge the PR to the release* branch. After the release* branch was merged to the master branch, the versions will be released automatically.