Lines Matching +full:js +full:- +full:native +full:- +full:api
3 Diagnostic tooling is important to the consumers of Node.js. It is used both
8 The Node.js project has assessed the tools and the APIs which support those
12 * Tier 1 - Must always be working(CI tests passing) for all
13 Current and LTS Node.js releases. A release will not be shipped if the test
14 suite for the tool/API is not green. To be considered for inclusion
16 must exist in the Node.js CI so that it can be run as part of the release
19 release branches should break this tool/API if the next major release
25 * The tool must have a guide or other documentation in the Node.js GitHub
28 * The tool must only be using APIs exposed by Node.js as opposed to
32 * Tier 2 - Must be working(CI tests passing) for all
34 suite for the tool/API is not green. To be considered for inclusion
36 must exist in the Node.js CI so that it can be run as part of the release
42 * The tool must have a guide or other documentation in the Node.js GitHub
46 * Tier 3 - If possible its test suite
47 will be run at least nightly in the Node.js CI and issues opened for
50 * Tier 4 - Does not block shipping a release.
52 * Unclassified - tool/API is new or does not have the required testing in the
53 Node.js CI in order to qualify for a higher tier.
66 * If the tool is maintained by the Node.js Foundation GitHub organization.
70 * FFDC (F) - First failure data capture, easy to consume initial diagnostic
72 * Tracing (T) - use of logging to provide information about execution flow.
73 * Memory (M) - tools that provide additional information about memory
74 used in the Heap or by native code.
75 * Profiling (P) - tools that provide additional information about where
77 * AsyncFlow (A) - tools that provide additional insight into asynchronous
82 Any tool that might be used to investigate issues when running Node.js can
96 …| Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js …
97 …|-----------|---------------------------|-------------------------------|-------------------------…
103 …| Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js …
104 …|-----------|---------------------------|-------------------------------|-------------------------…
109 …| Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated wi…
110 …|-----------|--------------------------------------|-------------------------------|--------------…
112 …| Profiling | --prof/--prof-process flags | Yes | Yes …
113 …| Profiling | V8 CodeEventHandler API | Partial (V8 Tests) | Yes …
114 …| Profiling | V8 --interpreted-frames-native-stack | Yes | Yes …
119 …| Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js …
120 …|-----------|---------------------------|-------------------------------|-------------------------…
125 …| Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js …
126 …|-----------|---------------------------|-------------------------------|-------------------------…
127 …| FFDC | node-report | No | No …
129 …| Memory | node-heapdump | No | No …
132 …| AsyncFlow | Async Hooks (API) | ? | Yes …
133 …| Debugger | V8 Debug protocol (API) | No | Yes …
137 …| Debugger | Chakracore - time-travel | No | Data source only …
138 …| Tracing | trace_events (API) | No | Yes …
146 …| Profiling | node-clinic | No | No …