69c22889ab
* Make sure package is published under @elastic org namespace * Preparing packages/ for Kibana-related packages * Folder structure mirrors package name * Add note on naming consistency * s/packages/node modules/ for removing potention confusion with Kibana system packages * Prefixing the eslint rule with package scope (i.e. org namespace) * Adding README * Bumping up version for release * Adding repository information to package.json * Bumping up version for release * URL-encoding repository link + bumping up version for release * Using published version
7 lines
409 B
Markdown
7 lines
409 B
Markdown
## Kibana-related node modules
|
|
|
|
This folder contains node modules that are created by Kibana developers, for use in Kibana and its plugins.
|
|
|
|
For each such node module, create a sub-folder in this folder. The path/name of the folder should mirror the `name` in the node module's `package.json`. To publish the node module as an npm package, `cd` into the package's sub-folder, and run `npm publish` as usual.
|
|
|