Displaying 1 to 20 from 23 results

leakage - πŸ› Memory leak testing for node.


Memory leak testing for node. Javascript memory footprinting using your favorite test runner.

flamebearer - Blazing fast flame graph tool for V8 and Node πŸ”₯


A blazing fast flame graph tool for Node and V8. Used to visualize and explore performance profiling results. Designed to produce fast, lightweight flame graphs that remain responsive even on really big input.

node-webkit-agent - NodeJS agent for WebKit devtools front-end


This module is an implementation of Chrome developer tools protocol. It is still pretty much a work in progress and only heap and CPU profilers are working right now. Help is wanted to finish implementing debugger, networking and console agents as well as a implementing from scratch a flamegraphs agent. This module allows you to debug and profile remotely your nodejs applications leveraging the following features by re-using the built-in devtools front-end that comes with any webkit-based browsers such as Chrome or Safari.




Javascript .NET


Javascript .NET integrates Google's V8 Javascript engine and exposes it to the CLI environment. Javascript .NET compiles (at runtime) and executes scripts directly from .NET code. It allows CLI objects to be exposed and manipulated directly from the executed Javascript.

V8.NET


A fairly non-abstracted wrapper for Google's V8 JavaScript engine.

v8sharp


v8sharp started as a research project to see if it was possible to host Google's new V8 javascript engine from within Microsoft .NET. It could be used to create an extensibility model or application automation model that could be accessed via scripting technologies.


to-fast-properties - Force V8 to use fast properties for an object


Read more.Use %HasFastProperties(object) and --allow-natives-syntax to check whether an object already has fast properties.

stackman - He is like Batman, but for Node.js stack traces


Give Stackman an error and he will give an array of stack frames with extremely detailed information for each frame in the stack trace.With Stackman you get access to the actual source code and surrounding lines for where the error occurred, you get to know if it happened inside a 3rd party module, in Node.js or in your own code. For a full list of information, check out the API below.

core - Server core components which are a part of ONLYOFFICE Document Server


Server core components which are a part of ONLYOFFICE Document Server. Enable the conversion between the most popular office document formats: DOC, DOCX, ODT, RTF, TXT, PDF, HTML, EPUB, XPS, DjVu, XLS, XLSX, ODS, CSV, PPT, PPTX, ODP.If you have any problems with or questions about ONLYOFFICE Document Server, please visit our official forum to find answers to your questions: dev.onlyoffice.org or you can ask and answer ONLYOFFICE development questions on Stack Overflow.

v8-argv - Proxy v8 argv (including harmony) to v8/node while forwarding the remaining arguments to a custom script


Proxy v8 argv (including harmony) to v8/node while forwarding the remaining arguments to a custom script.v8-argv is available on npm.

c8 - collect test coverage using v8's inspector


Code-coverage using v8's Inspector that's compatible with Istanbul's reporters.The above example will collect coverage for foo.js using v8's inspector.

v8-to-istanbul - convert from v8 coverage format to istanbul's format


converts from v8 coverage format to istanbul's coverage format.

JavaScriptEngineSwitcher - JavaScript Engine Switcher determines unified interface for access to the basic features of popular JavaScript engines (MSIE JavaScript Engine for


JavaScript Engine Switcher determines unified interface for access to the basic features of popular JavaScript engines (MSIE JavaScript Engine for .Net, Microsoft ClearScript.V8, Jurassic, Jint, ChakraCore and VroomJs). This library allows you to quickly and easily switch to using of another JavaScript engine.If you have used the JavaScript Engine Switcher version 1.X, then I recommend to first read “How to upgrade applications to version 2.X” section of the documentation.

babel-plugin-source-map-support - A Babel plugin which automatically makes stack traces source-map aware


In conjunction with the source-map-support module, which must be installed separately, this statement hooks into the v8 stack-trace API to translate call sites in the transpiled code back to their corresponding locations in the original code. Note: this only works in environments which support the v8 stack-trace API (e.g. Node.js and Chrome), though it's harmless in other environments.