Thank you for considering to contribute to Craft.js!
From proofreading, translating, writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests, or writing code, there are many ways to contribute. Upon contribution as per the all-contributors specification, your profile will be recognised in our README's contributors section.
To get started right away, have a look at our project tracker to check out a list of things that we'd like to work on right now.
If you are interested in proposing a new feature or have found a bug that you'd like to fix, please file a new issue.
master
git clone https://github.com/your-name/craft.js
cd craft.js
> yarn install
> yarn dev
> yarn clean # clean all build files from all packages in the monorepo
> yarn build # create production build for all craftjs packages
> yarn lint # run tests across the monorepo
Craft.js uses Changesets to track and publish new releases.
Therefore, when you submit a change that affects functionality (ie: fix a bug or add a new feature) to one of the packages (in the /packages/
folder), then you will need to create a new Changeset by running the following command:
yarn changeset
Typos and changes made to the /examples
or the main /site
do not require a changeset.
Currently Craft.js is still using major version 0.y.z, where y is only incremented when there's a major/breaking change. Hence, when creating a changeset:-
patch
minor
major
should not be used at the momentBy contributing, you agree that your contributions will be licensed under MIT License.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。