Internal tool for building Roc extensions.
Add this module as a dev dependency to the Roc extension that you want to manage. Then you can connect npm scripts to the commands that this module exposes.
You can use the short name rid
as an alternative to roc-internal-dev
if you don't want to write out the entire name.
"scripts": {
"build": "rid build",
// ...
}
A useful tip is to add an alias to rid that makes it easier to work with in the project.
"scripts": {
"start": "rid",
// ...
}
It is then possible to run all possible commands using npm start <command>
.
It is important to add the extension itself to the package.json
for roc-internal-dev
to be able to generate documentation.
Example
{
"name": "roc-package-module",
...
"roc": {
"packages": [
"./lib/index.js"
]
}
}
Please see here for all of the commands.
- Fixed support for Node 4. #13
- Added command for running
npm test
in extensions usingrid test:alias
.
- Makes it possible to use
yarn
overnpm
when usingrid link
.
- Now runs
clean
when runningrelease
.
- Fixed a bug in the release command.
- Added
--next
flag to be used withrelease
command.
- Added missing
bin/
folder when publishing to npm.
- Updated to work with the latest version of
roc
. - Now uses
extensions/
instead ofpackages/
for the extensions. - Changed from running
lint-alias
tolint
on release by default and added option to use alias with--use-alias
. - Updated to use ESLint 3.0.
- Added new command,
rnm
, for removingnode_modules
in extensions directory.
- Fixed regression from the previous release.
- Added a way to link additional modules when running the
link
command, seerid link -h
for more info.
- This release was botched, see 1.3.1 instead.
- Now uses
lint-alias
instead ofalias
when doing the release.
- Now generates new documentation when creating a new release.
- Solved a bug in the release script.
- Made a correct reference to getConfiguration from
roc
.
- More generic way to handle extensions, brings support for plugins.
- New better way to generate documentation.
- Initial version