|
1
|
# tiny-warning 🔬⚠️
|
|
2
|
|
|
3
|
[](https://travis-ci.org/alexreardon/tiny-warning)
|
|
4
|
[](https://www.npmjs.com/package/tiny-warning) [](https://www.npmjs.com/package/tiny-warning) [](https://david-dm.org/alexreardon/tiny-warning)
|
|
5
|
[](https://www.npmjs.com/package/tiny-warning)
|
|
6
|
[](https://www.npmjs.com/package/tiny-warning)
|
|
7
|
|
|
8
|
A tiny [`warning`](https://www.npmjs.com/package/warning) alternative.
|
|
9
|
|
|
10
|
```js
|
|
11
|
import warning from 'tiny-warning';
|
|
12
|
|
|
13
|
warning(truthyValue, 'This should not log a warning');
|
|
14
|
|
|
15
|
warning(falsyValue, 'This should log a warning');
|
|
16
|
// console.warn('Warning: This should log a warning');
|
|
17
|
```
|
|
18
|
|
|
19
|
## API: `(condition: mixed, message: string) => void`
|
|
20
|
|
|
21
|
- `condition` is required and can be anything
|
|
22
|
- `message` is an required string that will be passed onto `console.warn`
|
|
23
|
|
|
24
|
## Why `tiny-warning`?
|
|
25
|
|
|
26
|
The [`library: warning`](https://www.npmjs.com/package/warning) supports passing in arguments to the `warning` function in a sprintf style `(condition, format, a, b, c, d, e, f)`. It has internal logic to execute the sprintf substitutions. `tiny-warning` has dropped all of the sprintf logic. `tiny-warning` allows you to pass a single string message. With [template literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals) there is really no need for a custom message formatter to be built into the library. If you need a multi part message you can just do this: `warning(condition, 'Hello, ${name} - how are you today?')`
|
|
27
|
|
|
28
|
## Dropping your `warning` for kb savings!
|
|
29
|
|
|
30
|
We recommend using [`babel-plugin-dev-expression`](https://www.npmjs.com/package/babel-plugin-dev-expression) to remove `warning` calls from your production build. This saves you kb's as well as avoids logging warnings to the console for production.
|
|
31
|
|
|
32
|
What it does it turn your code that looks like this:
|
|
33
|
|
|
34
|
```js
|
|
35
|
warning(condition, 'My cool message that takes up a lot of kbs');
|
|
36
|
```
|
|
37
|
|
|
38
|
Into this
|
|
39
|
|
|
40
|
```js
|
|
41
|
if ('production' !== process.env.NODE_ENV) {
|
|
42
|
warning(condition, 'My cool message that takes up a lot of kbs');
|
|
43
|
}
|
|
44
|
```
|
|
45
|
|
|
46
|
Your bundler can then drop the code in the `"production" !== process.env.NODE_ENV` block for your production builds
|
|
47
|
|
|
48
|
Final result:
|
|
49
|
|
|
50
|
```js
|
|
51
|
// nothing to see here! 👍
|
|
52
|
```
|
|
53
|
|
|
54
|
> For `rollup` use [rollup-plugin-replace](https://github.com/rollup/rollup-plugin-replace) and set `NODE_ENV` to `production` and then `rollup` will treeshake out the unused code
|
|
55
|
>
|
|
56
|
> [`Webpack` instructions](https://webpack.js.org/guides/production/#specify-the-mode)
|
|
57
|
|
|
58
|
## Builds
|
|
59
|
|
|
60
|
- We have a `es` (EcmaScript module) build (because you _know_ you want to deduplicate this super heavy library)
|
|
61
|
- We have a `cjs` (CommonJS) build
|
|
62
|
- We have a `umd` (Universal module definition) build in case you needed it
|
|
63
|
|
|
64
|
We expect `process.env.NODE_ENV` to be available at module compilation. We cache this value
|
|
65
|
|
|
66
|
## That's it!
|
|
67
|
|
|
68
|
🤘
|