1 | Before opening a pull request
|
2 | =============================
|
3 |
|
4 | - [Wiki article on contributing to Node Inspector](https://github.com/node-inspector/node-inspector/wiki/Contributing)
|
5 | - [Developer's guide](https://github.com/node-inspector/node-inspector/wiki/Developer%27s-Guide)
|
6 |
|
7 | Before opening an issue
|
8 | =======================
|
9 |
|
10 | In order to facilitate reproduction of issues, please always provide the following info:
|
11 |
|
12 | - node-inspector version (`node-inspector --version`)
|
13 | - node.js version (`node --version`)
|
14 | - operating system name and version
|
15 |
|
16 | Please upgrade to the newest version before opening an issue:
|
17 |
|
18 | `npm install -g node-inspector`
|
19 |
|
20 | and check if it still is reproducible.
|
21 |
|
22 | If the issue started happening after a recent upgrade, you can downgrade to an older version
|
23 | of Node Inspector with a command like this:
|
24 |
|
25 | `npm install -g node-inspector@0.8.3`
|
26 |
|
27 | Providing information if the bug is a recent regression will also facilitate its handling.
|
28 |
|
29 | Click [here](https://github.com/node-inspector/node-inspector/releases) to find out
|
30 | what are the available versions.
|
31 | Alternatively you can also use the following command:
|
32 |
|
33 | `npm view node-inspector`
|