mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
4cd2360db4
* Remove duplicate dep, x-pack/yarn.lock (#26642) * [npm] prepare @kbn/datemath for publishing (#26559) We need to share `@kbn/datemath` with `@elastic/eui`, and rather than making them rely on Kibana for their dependencies we've decided to republish `@kbn/datemath` as `@elastic/datemath`. This isn't something we want to do often, so please check with the platform team if you'd like to do this for another module.
66 lines
2.6 KiB
Markdown
66 lines
2.6 KiB
Markdown
# Kibana-related packages
|
|
|
|
This folder contains packages that are intended for use in Kibana and Kibana
|
|
plugins.
|
|
|
|
tl;dr:
|
|
|
|
- Don't publish to npm registry
|
|
- Always use the `@kbn` namespace
|
|
- Always set `"private": true` in `package.json`
|
|
|
|
## Using these packages
|
|
|
|
We no longer publish these packages to the npm registry. Now, instead of
|
|
specifying a version when including these packages, we rely on yarn workspaces,
|
|
which sets up a symlink to the package.
|
|
|
|
For example if you want to use the `@kbn/i18n` package in Kibana itself, you
|
|
can specify the dependency like this:
|
|
|
|
```
|
|
"@kbn/i18n": "1.0.0"
|
|
```
|
|
|
|
However, if you want to use this from a Kibana plugin, you need to use a `link:`
|
|
dependency and account for the relative location of the Kibana repo, so it would
|
|
instead be:
|
|
|
|
```
|
|
"@kbn/i18n": "link:../../kibana/packages/kbn-i18n"
|
|
```
|
|
|
|
How all of this works is described in more detail in the
|
|
[`@kbn/pm` docs](./kbn-pm#how-it-works).
|
|
|
|
## Creating a new package
|
|
|
|
Create a new sub-folder. The name of the folder should mirror the `name` in the
|
|
package's `package.json`. E.g. if the name is `@kbn/i18n` the folder name
|
|
should be `kbn-i18n`.
|
|
|
|
All new packages should use the `@kbn` namespace, and should be marked with
|
|
`"private": true`.
|
|
|
|
## Unit tests for a package
|
|
|
|
Currently there are two patterns used to test packages, one using Mocha and one using Jest. These patterns emerged out of convention and we'd like to make them more similar to each other in the near future.
|
|
|
|
### 1. Mocha
|
|
Today a package can follow the pattern of having a `__tests__` directory in each source code directory of a package which contains the tests for that module. These are usually run by Mocha.
|
|
|
|
If a package's tests should be run with Mocha, you'll have to opt-in to run them by appending the package's test file pattern(s) to Kibana's `tasks/config/simplemocha.js` file. These will then be run by the unit test runner.
|
|
|
|
* `yarn test` or `yarn grunt test` runs all unit tests.
|
|
* `node scripts/mocha` runs all Mocha tests.
|
|
|
|
### 2. Jest
|
|
A package can also follow the pattern of having `.test.js` files as siblings of the source code files, and these run by Jest.
|
|
|
|
A package using the `.test.js` naming convention will have those tests automatically picked up by Jest and run by the unit test runner, currently mapped to the Kibana `test` script in the root `package.json`.
|
|
|
|
* `yarn test` or `yarn grunt test` runs all unit tests.
|
|
* `node scripts/jest` runs all Jest tests in Kibana.
|
|
|
|
----
|
|
Each package can also specify its own `test` script in the package's `package.json`, for cases where you'd prefer to run the tests from the local package directory.
|