Contributing
#
What are the files in each package?#
Publishing a new versionSelect the branch you want to publish from and enter latest
or prerelease
as the distTag
.
For production release use master
branch and latest
.
For prereleases use any branch and the prerelease
dist tag.
The versioning is based on conventional commit history (see the Contributing section).
#
Adding a new packageSee the documentation for create-nexus-package
. To summarize:
Create a new folder and cd
to it.
Initialize a new package using the @uplit-ltd/create-nexus-package initializer.
#
Working with local packagesThere's some weirdness with yarn link
. The most reliable way seems to be to use npm link
. Also
if the package depends on react
you may have to alias that to the app react
to avoid duplicate
react versions (and hooks failing).
Additionally you may need to alias @apollo/client
and its own react
version to the app.
Don't forget to run yarn build
after every change.
You might have to wipe node_modules/.cache
in your app if you ran into duplicate react issue.
See react docs for more details.