Please take a moment to review this document in order to make the contribution process straightforward and effective for everyone involved.
Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
Write less code, Let shuvi do more.
shuvi
is a monorepo, meaning it is divided into independent sub-packages.
These packages can be found in the packages/
directory.
Type definitions for shuvi application.
Core components.
Core runtime of application.
React runtime for application.
Assemble other packages for setting up the development server, building production builds.
Reusable logic within the project.
Generally reusable logic.
configuring for webpack, babel, etc.
Type definitions for shuvi.
$ curl https://sh.rustup.rs -sSf | sh
docs: https://doc.rust-lang.org/cargo/getting-started/installation.html
-
Clone the repo with
git clone https://github.com/liximomo/shuvi
-
Run
pnpm i
in the root folder. -
Run
pnpm build
in the root folder.
-
Open two terminal at the root folder.
-
Run
pnpm dev
Once it is done, you can run shuvi cli by pnpm shuvi
in another terminal. It will serve the application in the specified dir.
e.g.
pnpm shuvi dev test/fixtures/basic
Shuvi uses changesets to manage monorepo versions and publish.
After writing code and complete test, run pnpm changeset
to add a changeset, or run pnpm changeset pre enter xxx
to add a changeset with prereleases version. And then bring this changeset file to git.