Lines Matching refs:tool

14   suite for the tool/API is not green. To be considered for inclusion
19   release branches should break this tool/API if the next major release
21   * The maintainers of the tool must remain responsive when there
23   * The tool must be actively used by the ecosystem;
24   * The tool must be heavily depended on;
25   * The tool must have a guide or other documentation in the Node.js GitHub
27   * The tool must be working on all supported platforms;
28   * The tool must only be using APIs exposed by Node.js as opposed to
30   * The tool must be open source.
34   suite for the tool/API is not green. To be considered for inclusion
38   * The maintainers of the tool must remain responsive when
40   * The tool must be actively used by the ecosystem;
41   * The tool must be heavily depended on;
42   * The tool must have a guide or other documentation in the Node.js GitHub
44   * The tool must be open source.
52 * Unclassified - tool/API is new or does not have the required testing in the
55 The choice of which tier a particular tool will be assigned to, will be a
59 * If the tool fits into a key category as listed below.
60 * Whether the tool is actively used by the ecosystem.
62 * Impact to the overall ecosystem if the tool is not working.
66 * If the tool is maintained by the Node.js Foundation GitHub organization.
80 ## Adding a tool to this list
82 Any tool that might be used to investigate issues when running Node.js can
83 be added to the list. If there is a new tool that should be added to the
148 | M/T       | eBPF tracing tool         | No                            | No                      |…