├── examples
│ ├── with-nextjs
│ ├── with-nodejs
│ ├── with-react
│ ├── with-vanilla
│ ├── with-vue
├── packages
│ ├── auth
│ │ ├── core
│ │ ├── edge
│ │ ├── nextjs
│ │ ├── node
│ │ ├── react
│ │ ├── vue
│ ├── auth-ui
│ │ ├── elements
│ │ ├── react
│ │ ├── shared
│ │ ├── vue
├── package.json
├── pnpm-lock.yaml
├── pnpm-workspace.yaml
├── turbo.json
├── .gitignore
└── ...
with-nextjs, with-nodejs,with-react, with-vue, with-vanilla
Install with no lockfile.
yarn install --no-lockfileSet environment variables.
Start dev server
yarn devIt's recommended that using local npm registry server in order to test distributed packages.
https://verdaccio.org/docs/what-is-verdaccio
pnpm verdaccio-start
Login with
pnpm login --registry http://localhost:4873Make sure that you are in the right package to publish and run
pnpm publish --registry http://localhost:4873Then add this to namespace and registry to the example project's .npmrc in order to test.
With this package manager will download packages from the local registry instead of npmjs.com
@scute:registry=http://localhost:4873To generate a new changeset, run pnpm changeset in the root of the repository. The generated markdown files in the .changeset directory should be committed to the repository.
- Run
pnpm changeset version. This will bump the versions of the packages previously specified withpnpm changeset(and any dependents of those) and update the changelog files. - Run
pnpm install. This will update the lockfile and rebuild packages. - Commit the changes.
- Run
pnpm publish -r. This command will publish all packages that have bumped versions not yet present in the registry. - You can publish to local
verdaccioregistry server withpnpm publish -r --registry http://localhost:4873command.
Docs
https://github.com/changesets/changesets/blob/main/docs/intro-to-using-changesets.md