stack-utils-node-internals

    1.0.1 • Public • Published

    stack-utils-node-internals NPM version mit license NPM monthly downloads npm total downloads

    An array of node internals that can be cleaned up from stack traces

    code climate code style linux build windows build code coverage dependency status paypal donate

    You might also be interested in stack-utils.

    Table of Contents

    (TOC generated by verb using markdown-toc)

    Install

    Install with npm

    $ npm install stack-utils-node-internals --save
    

    or install using yarn

    $ yarn add stack-utils-node-internals
    

    Usage

    For more use-cases see the tests

    const stackUtilsNodeInternals = require('stack-utils-node-internals')
     
    const regexps = stackUtilsNodeInternals()
    console.log(regexps)
     
    const natives = stackUtilsNodeInternals.natives
    console.log(natives)
    // => [ 'internal/bootstrap_node',
    //  '_debug_agent',
    //  '_debugger',
    //  'assert',
    //  'buffer',
    //  'child_process',
    //  'console',
    //  'constants',
    //  'crypto',
    //  'cluster',
    //  'dgram',
    //  'dns',
    //  'domain',
    //  'events',
    //  'fs',
    //  'http',
    //  '_http_agent',
    //  '_http_client',
    //  '_http_common',
    //  '_http_incoming',
    //  '_http_outgoing',
    //  '_http_server',
    //  'https',
    //  '_linklist',
    //  'module',
    //  'net',
    //  'os',
    //  'path',
    //  'process',
    //  'punycode',
    //  'querystring',
    //  'readline',
    //  'repl',
    //  'stream',
    //  '_stream_readable',
    //  '_stream_writable',
    //  '_stream_duplex',
    //  '_stream_transform',
    //  '_stream_passthrough',
    //  '_stream_wrap',
    //  'string_decoder',
    //  'sys',
    //  'timers',
    //  'tls',
    //  '_tls_common',
    //  '_tls_legacy',
    //  '_tls_wrap',
    //  'tty',
    //  'url',
    //  'util',
    //  'v8',
    //  'vm',
    //  'zlib',
    //  'internal/buffer',
    //  'internal/child_process',
    //  'internal/cluster/child',
    //  'internal/cluster/master',
    //  'internal/cluster/round_robin_handle',
    //  'internal/cluster/shared_handle',
    //  'internal/cluster/utils',
    //  'internal/cluster/worker',
    //  'internal/errors',
    //  'internal/freelist',
    //  'internal/fs',
    //  'internal/linkedlist',
    //  'internal/net',
    //  'internal/module',
    //  'internal/process/next_tick',
    //  'internal/process/promises',
    //  'internal/process/stdio',
    //  'internal/process/warning',
    //  'internal/process',
    //  'internal/querystring',
    //  'internal/process/write-coverage',
    //  'internal/readline',
    //  'internal/repl',
    //  'internal/socket_list',
    //  'internal/url',
    //  'internal/util',
    //  'internal/v8_prof_polyfill',
    //  'internal/v8_prof_processor',
    //  'internal/streams/lazy_transform',
    //  'internal/streams/BufferList',
    //  'internal/streams/legacy',
    //  'v8/tools/splaytree',
    //  'v8/tools/codemap',
    //  'v8/tools/consarray',
    //  'v8/tools/csvparser',
    //  'v8/tools/profile',
    //  'v8/tools/profile_view',
    //  'v8/tools/logreader',
    //  'v8/tools/tickprocessor',
    //  'v8/tools/SourceMap',
    //  'v8/tools/tickprocessor-driver',
    //  'node-inspect/lib/_inspect',
    //  'node-inspect/lib/internal/inspect_client',
    //  'node-inspect/lib/internal/inspect_repl',
    //  'bootstrap_node',
    //  'node' ]

    Related

    Contributing

    Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
    Please read the contributing guidelines for advice on opening issues, pull requests, and coding standards.
    If you need some help and can spent some cash, feel free to contact me at CodeMentor.io too.

    In short: If you want to contribute to that project, please follow these things

    1. Please DO NOT edit README.md, CHANGELOG.md and .verb.md files. See "Building docs" section.
    2. Ensure anything is okey by installing the dependencies and run the tests. See "Running tests" section.
    3. Always use npm run commit to commit changes instead of git commit, because it is interactive and user-friendly. It uses commitizen behind the scenes, which follows Conventional Changelog idealogy.
    4. Do NOT bump the version in package.json. For that we use npm run release, which is standard-version and follows Conventional Changelog idealogy.

    Thanks a lot! :)

    Building docs

    Documentation and that readme is generated using verb-generate-readme, which is a verb generator, so you need to install both of them and then run verb command like that

    $ npm install verbose/verb#dev verb-generate-readme --global && verb
    

    Please don't edit the README directly. Any changes to the readme must be made in .verb.md.

    Running tests

    Clone repository and run the following in that cloned directory

    $ npm install && npm test
    

    Author

    Charlike Mike Reagent

    License

    Copyright © 2016-2017, Charlike Mike Reagent. Released under the MIT License.


    This file was generated by verb-generate-readme, v0.4.3, on March 09, 2017.
    Project scaffolded using charlike cli.

    Install

    npm i stack-utils-node-internals

    DownloadsWeekly Downloads

    5,699

    Version

    1.0.1

    License

    MIT

    Last publish

    Collaborators

    • vanchoy
    • tunnckocore