代码拉取完成，页面将自动刷新
The Scratch Parser is a Node.js module that parses and validates Scratch projects.
npm install scratch-parser
var fs = require('fs');
var parser = require('scratch-parser');
var buffer = fs.readFileSync('/path/to/project.sb2');
parser(buffer, function (err, project) {
if (err) // handle the error
// do something interesting
});
In addition to the _meta data described above, Scratch projects include an attribute called info that may include the following:
| Key | Description |
|---|---|
flashVersion |
Installed version of Adobe Flash |
swfVersion |
Version of the Scratch editor used to create the project |
userAgent |
User agent used to create the project |
savedExtensions |
Array of Scratch Extensions used in the project |
npm test
make coverage
make benchmark
This project uses semantic release to ensure version bumps follow semver so that projects using the config don't break unexpectedly.
In order to automatically determine the type of version bump necessary, semantic release expects commit messages to be formatted following conventional-changelog.
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
subject and body are your familiar commit subject and body. footer is
where you would include BREAKING CHANGE and ISSUES FIXED sections if
applicable.
type is one of:
fix: A bug fix Causes a patch release (0.0.x)
feat: A new feature Causes a minor release (0.x.0)
docs: Documentation only changesstyle: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)refactor: A code change that neither fixes a bug nor adds a featureperf: A code change that improves performance May or may not cause a minor release. It's not clear.
test: Adding missing tests or correcting existing testsci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)chore: Other changes that don't modify src or test filesrevert: Reverts a previous commitUse the commitizen CLI to make commits formatted in this way:
npm install -g commitizen
npm install
Now you're ready to make commits using git cz.
If you're committing a change that will require changes to existing code, ensure your commit specifies a breaking change. In your commit body, prefix the changes with "BREAKING CHANGE: " This will cause a major version bump so downstream projects must choose to upgrade the config and will not break the build unexpectedly.
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。