Debug Node.js code with Chrome Developer Tools.

Overview

ironNode
NPM Version Build Status Codacy Badge Dependency Status devDependency Status NPM Downloads Massachusetts Institute of Technology (MIT) Donate

Debug Node.js code with Chrome Developer Tools on Linux, Windows and OS X.

This software aims to make things easier 😄 . With ironNode you have the full power of JavaScript debugging within Chrome Developer Tools.

Installation

npm install iron-node -g;

Usage

The usage is the same as node. Use iron-node instead of node.
Keep in mind to place the keyword debugger; to a place where you want to stop. Run a debug session with the given JavaScript file.

iron-node PATH_TO_NODE_JS_FILE [--customparm1=foo --customparm2=bar];

Demo

Version details

More screenshots and demos

Documentation

Support

Contributing

License

Comments
  • process.stdout.write does not output to DevTools console?

    process.stdout.write does not output to DevTools console?

    The app i was testing with uses bunyan which logs to the console. However when running with iron-node the console/stdout is suppressed for some reason.

    enhancement not a bug 
    opened by krohrsb 26
  • NODE_PATH environment variable is ignored

    NODE_PATH environment variable is ignored

    Reproduce

    The NODE_PATH environment variable is set correctly, but it seems to be ignored when I do this:

        "debug:unit": "NODE_PATH=source iron-node source/test/unit/debug.js",
    

    This works fine:

        "test:unit": "NODE_PATH=source babel-node source/test/unit/index.js",
    

    debug.js looks like this:

    require('babel-core/register');
    require('./index.js');
    

    As you can see, the test directory containing debug.js is inside the source directory.

    enhancement 
    opened by ericelliott 25
  • "Module version mismatch" error

    This is in the console, and it's not starting the server because of it. Hopefully there's enough info in the screenshot for versions - but please let me know if you need more.

    screen shot 2015-10-08 at 14 09 48 third party native module 
    opened by remy 22
  • iron-node do not work / starts with an error

    iron-node do not work / starts with an error

    i installed with

    npm install -g iron-node

    and tried a simple file including a "debugger;" statement.

    i call it with "iron-node ./test.js" and a dialog-error pops up:

    Starting iron-node without further arguments also creates the same error message.

    A JavaScript error occurred in the main process

    Uncaught Exception: TypeError: app.getPath is not a function at Config (/usr/local/lib/node_modules/iron-node/app/config.js:56:35) at initializeApplication (/usr/local/lib/node_modules/iron-node/app/index.js:35:41) at EventEmitter. (/usr/local/lib/node_modules/iron-node/app/index.js:48:15) at emitOne (events.js:95:20) at EventEmitter.emit (events.js:182:7)

    Do you have any idea how to solve this issue?

    My system is Ubuntu 16.04 LTS 64-bit.

    Thx.

    opened by weingaunity 21
  • `window` is defined, breaking platform-detection in node environment.

    `window` is defined, breaking platform-detection in node environment.

    We have code that tests its environment:

    if (typeof window === 'undefined') {
      // node stuff
    } else {
      // browser stuff.
    }
    

    To use iron-node on node apps with such tests, window from iron-node cannot be visible to the app under debug.

    help wanted discussion 
    opened by johnjbarton 19
  • Debugger crash when script call process.exit()

    Debugger crash when script call process.exit()

    screenshot 2015-08-10 15 48 34

    This problem happens only when I'm running the script using iron-node and not when running the script using node or node debug. To be more precise: normally the script runs my jasmine test suite and exits. In iron-node is crashes before running the tests.

    bug 
    opened by mik01aj 19
  • How to use with mocha on Linux?

    How to use with mocha on Linux?

    I have seen your post about iron-node with mocha on Windows. However, I am not sure how to map that; my attempts have failed so far. I don't have that first file C:\Users\Stephan\AppData\Roaming\npm\mocha.cmd. I have /usr/local/bin/mocha, a link to ../lib/node_modules/mocha/bin/mocha with the content you have in file two. Adding the

    process.argv[0] = "iron-node.cmd";
    

    is the problem - why that on Windows, i.e., what was the intention? And what should I do on linux instead?

    I tried to change node to iron-node in _mocha, but that leads to

    Error: Cannot find module './options'(…)
        error @ app.js:19
        emitOne @ events.js:77
        emit @ events.js:169
        window.onerror @ /usr/local/lib/node_modules/iron-node/node_modules/electron-prebuilt/dist/resources/atom.asar/rende…:76
    

    So... any hints? :)

    opened by michael-brade 18
  • Breakpoints aren't hit

    Breakpoints aren't hit

    I've read that I need to add "debugger;", which I did, but it still doesn't break on startup and none of the breakpoints I set are hit either. What can be the reason? (It's an express app without any fancy stuff or frameworks at the moment.)

    (Plus, I have no idea what to do with the left pane where it lists part of the package.json and tells me there is no readme.)

    help wanted need feedback electron 
    opened by CherryDT 12
  • debugger is not being hit on OSX

    debugger is not being hit on OSX

    Currently can't use IronNode due to breakpoints being cleared upon reload on OS X (cmd-R).

    breakpointscleared

    Is this a known bug? Is there a workaround?

    Also, why in the world does it not honor debugger; statements?

    help wanted OS X electron 
    opened by Qix- 11
  • Support for code piped through stdin

    Support for code piped through stdin

    This would allow any transpiler to be used on the fly without extra files or configuration.

    Examples:

    • babel app.es6 | node-iron
    • coffee -p app.coffee | node-iron
    • etc...
    enhancement 
    opened by franciscolourenco 11
  • Give love to left frame

    Give love to left frame

    I understand the importance of the left frame for your own good, but it would be even greater if it would be useful for the debugged project ;) I think the share buttons are pretty useless and could be replaced with a single link to project's homepage, whereas the donation button could be more exposed.

    I also imagine very good usages for this frame (all while keeping the donation button and link to homepage). If user could inject any HTML he wants the tool could be used for very nice and various unintended situations:

    • Training exercices: left frame gives the context, the goal, and user has to edit the code directly in debugger to make it work
    • General instructions: tell your co-workers about project specifics that may impact the debugging session, maybe tips about dev environment…
    • This could even be used to add some debugging and profiling pro-tips if nothing is specified by user
    discussion 
    opened by naholyr 11
  • ⬆️ Bump electron from 2.0.0 to 18.3.7

    ⬆️ Bump electron from 2.0.0 to 18.3.7

    Bumps electron from 2.0.0 to 18.3.7.

    Release notes

    Sourced from electron's releases.

    electron v18.3.7

    Release Notes for v18.3.7

    Fixes

    • Fixed WCO not responding to touch events on windows. #35177 (Also in 19, 20)
    • Fixed webContents.getUserAgent() incorrectly returning an empty string unless previously set. #35130 (Also in 17, 19, 20)
    • Fixed an issue in which calling setBounds() after e.preventDefault in a 'will-move' or 'will-resize' event wouldn't change the window's shape until the mouse button was released. #35082 (Also in 19, 20)
    • Fixed context menu not showing all items on macOS when dock is not hidden. #35198 (Also in 19)
    • None. #35171 (Also in 19, 20)

    Other Changes

    • Fixed page size always being restricted to 4k on Linux arm64. #35184
    • Security: backported fix for CVE-2022-2478. #35099
    • Security: backported fix for chromium:1334864. #35097

    electron v18.3.6

    Release Notes for v18.3.6

    Fixes

    • Fixed a crash when calling BrowserWindow.setEnabled(). #34973 (Also in 19, 20)
    • Fixed a potential crash when changing window settings after initializing WCO with an invalid titleBarStyle. #34873 (Also in 17, 19, 20)
    • Fixed alwaysOnTop BrowserWindow option for X11 Linux. #34911 (Also in 19, 20)
    • Fixed an issue where BrowserWindows on macOS were incorrectly marked as resizable. #34907 (Also in 19, 20)
    • Fixed an issue where Windows Control Overlay buttons did not respect maximizable/minimizable/closable states of a BrowserWindow. #34720 (Also in 17, 19, 20)
    • Fixed an issue where calling BrowserWindow.setRepresentedFilename on macOS with titlebarStyle: 'hiddenInset' or titlebarStyle: 'hidden' inadvertently moves the traffic light location. #34847 (Also in 19, 20)
    • Fixed an issue where some BrowserWindows opened from new links wouldn't properly load URLs. #34910 (Also in 19)
    • Fixed an issue where the minimize button with WCO enabled would incorrectly be highlighted in some cases. #34838 (Also in 17, 19, 20)
    • Fixed an issue with background colors being improperly applied to BrowserViews on Windows. #33478 (Also in 16)
    • Fixed empty app_id when running under wayland. #34877 (Also in 19, 20)
    • Fixed missing Sec-CH-UA headers and empty navigator.userAgentData. #34758 (Also in 17, 19, 20)
    • Fixed symbol generation on 32-bit Windows release builds. #35096 (Also in 19, 20)
    • Prevent brief display of "Ozone X11" in window title on Linux. #34943

    Other Changes

    • Backported fix for CVE-2022-2294. #34882
    • Security: backported fix for 1287804. #35102
    • Security: backported fix for 1333333. #34689
    • Security: backported fix for 1335054. #34687
    • Security: backported fix for 1335458. #34685
    • Security: backported fix for 1336014. #35004
    • Security: backported fix for 1339844. #35002
    • Security: backported fix for 1340335. #35000
    • Security: backported fix for 1340654. #34998
    • Security: backported fix for CVE-2022-2162. #34714
    • Security: backported fix for CVE-2022-2295. #34881

    electron v18.3.5

    Release Notes for v18.3.5

    ... (truncated)

    Changelog

    Sourced from electron's changelog.

    Breaking Changes

    Breaking changes will be documented here, and deprecation warnings added to JS code where possible, at least one major version before the change is made.

    Types of Breaking Changes

    This document uses the following convention to categorize breaking changes:

    • API Changed: An API was changed in such a way that code that has not been updated is guaranteed to throw an exception.
    • Behavior Changed: The behavior of Electron has changed, but not in such a way that an exception will necessarily be thrown.
    • Default Changed: Code depending on the old default may break, not necessarily throwing an exception. The old behavior can be restored by explicitly specifying the value.
    • Deprecated: An API was marked as deprecated. The API will continue to function, but will emit a deprecation warning, and will be removed in a future release.
    • Removed: An API or feature was removed, and is no longer supported by Electron.

    Planned Breaking API Changes (23.0)

    Removed: BrowserWindow scroll-touch-* events

    The deprecated scroll-touch-begin, scroll-touch-end and scroll-touch-edge events on BrowserWindow have been removed. Instead, use the newly available input-event event on WebContents.

    // Removed in Electron 23.0
    win.on('scroll-touch-begin', scrollTouchBegin)
    win.on('scroll-touch-edge', scrollTouchEdge)
    win.on('scroll-touch-end', scrollTouchEnd)
    

    // Replace with win.webContents.on('input-event', (_, event) => { if (event.type === 'gestureScrollBegin') { scrollTouchBegin() } else if (event.type === 'gestureScrollUpdate') { scrollTouchEdge() } else if (event.type === 'gestureScrollEnd') { scrollTouchEnd() } })

    Removed: webContents.incrementCapturerCount(stayHidden, stayAwake)

    The webContents.incrementCapturerCount(stayHidden, stayAwake) function has been removed. It is now automatically handled by webContents.capturePage when a page capture completes.

    const w = new BrowserWindow({ show: false })
    

    // Removed in Electron 23 w.webContents.incrementCapturerCount() </tr></table>

    ... (truncated)

    Commits
    Maintainer changes

    This version was pushed to npm by electron-nightly, a new releaser for electron since your current version.


    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • ⬆️ Bump css-what from 2.1.0 to 6.1.0

    ⬆️ Bump css-what from 2.1.0 to 6.1.0

    Bumps css-what from 2.1.0 to 6.1.0.

    Release notes

    Sourced from css-what's releases.

    v6.1.0

    • feat: Support pseudo elements with data (#762) 3be227a

    https://github.com/fb55/css-what/compare/v6.0.1...v6.1.0

    v6.0.1

    • Fix parsing column combinators after tag names 503570e

    https://github.com/fb55/css-what/compare/v6.0.0...v6.0.1

    v6.0.0

    Breaking Changes

    • Added ES6 module export (by @​spocke, fb55/css-what#680)
      • CommonJS is still provided for earlier NodeJS versions, but this change might cause issues with your build system. If they aren't trivially resolved, please open an issue!
    • Removed all options 5cad07b
      • BREAKING: Added a new value for ignoreCase: 'quirks' should ignore the case only in quirks mode.
      • BREAKING: Tags and attributes aren't lowercased anymore
    • Made selector types & actions enums 65121fe
    • Set empty namespace to null in attributes de367ca
    • Simplify stringify output 8a29466 b3e5e59

    Features

    • Support parsing column combinators 8030f67

    Fixes

    • Strip leading whitespace encapsulated in comments a812a1c
      • This used to be a way to sneak in descendant operators in front of selectors.

    Refactors

    • Switched parsing to numbers 65121fe
    • Restructured the parser to a big switch statement 7b6cc76

    Other

    • Adopted CSS Selector parsing tests from WPT 1881bba
    • Updated README to reflect changes b165a8d

    New Contributors

    Full Changelog: https://github.com/fb55/css-what/compare/v5.1.0...v6.0.0

    v5.1.0

    What's Changed

    Full Changelog: https://github.com/fb55/css-what/compare/v5.0.1...v5.1.0

    v5.0.1

    Fixes:

    ... (truncated)

    Commits
    • ee41dda 6.1.0
    • 3be227a feat: Support pseudo elements with data (#762)
    • 13ffc5b build(deps-dev): bump @​typescript-eslint/parser from 5.16.0 to 5.17.0 (#760)
    • 7d0cc2f build(deps-dev): bump @​typescript-eslint/eslint-plugin (#759)
    • 389d1b3 build(deps-dev): bump eslint from 8.11.0 to 8.12.0 (#758)
    • afd14e7 build(deps-dev): bump prettier from 2.6.0 to 2.6.1 (#757)
    • a1542de build(deps-dev): bump typescript from 4.6.2 to 4.6.3 (#756)
    • 41d9752 build(deps-dev): bump ts-jest from 27.1.3 to 27.1.4 (#755)
    • fed0407 build(deps): bump minimist from 1.2.5 to 1.2.6 (#754)
    • 96a2408 build(deps-dev): bump @​types/node from 17.0.22 to 17.0.23 (#753)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • ⬆️ Bump hosted-git-info from 2.6.0 to 2.8.9

    ⬆️ Bump hosted-git-info from 2.6.0 to 2.8.9

    Bumps hosted-git-info from 2.6.0 to 2.8.9.

    Changelog

    Sourced from hosted-git-info's changelog.

    2.8.9 (2021-04-07)

    Bug Fixes

    2.8.8 (2020-02-29)

    Bug Fixes

    • #61 & #65 addressing issues w/ url.URL implmentation which regressed node 6 support (5038b18), closes #66

    2.8.7 (2020-02-26)

    Bug Fixes

    • Do not attempt to use url.URL when unavailable (2d0bb66), closes #61 #62
    • Do not pass scp-style URLs to the WhatWG url.URL (f2cdfcf), closes #60

    2.8.6 (2020-02-25)

    2.8.5 (2019-10-07)

    Bug Fixes

    • updated pathmatch for gitlab (e8325b5), closes #51
    • updated pathmatch for gitlab (ffe056f)

    2.8.4 (2019-08-12)

    ... (truncated)

    Commits
    • 8d4b369 chore(release): 2.8.9
    • 29adfe5 fix: backport regex fix from #76
    • afeaefd chore(release): 2.8.8
    • 5038b18 fix: #61 & #65 addressing issues w/ url.URL implmentation which regressed nod...
    • 7440afa chore(release): 2.8.7
    • 2d0bb66 fix: Do not attempt to use url.URL when unavailable
    • f2cdfcf fix: Do not pass scp-style URLs to the WhatWG url.URL
    • e1b83df chore(release): 2.8.6
    • ff259a6 Ensure passwords in hosted Git URLs are correctly escaped
    • 624fd6f chore(release): 2.8.5
    • Additional commits viewable in compare view
    Maintainer changes

    This version was pushed to npm by nlf, a new releaser for hosted-git-info since your current version.


    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • ⬆️ Bump ini from 1.3.5 to 1.3.7

    ⬆️ Bump ini from 1.3.5 to 1.3.7

    Bumps ini from 1.3.5 to 1.3.7.

    Commits
    • c74c8af 1.3.7
    • 024b8b5 update deps, add linting
    • 032fbaf Use Object.create(null) to avoid default object property hazards
    • 2da9039 1.3.6
    • cfea636 better git push script, before publish instead of after
    • 56d2805 do not allow invalid hazardous string as section name
    • See full diff in compare view
    Maintainer changes

    This version was pushed to npm by isaacs, a new releaser for ini since your current version.


    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Child Processes don't show in the logs or in the source

    Child Processes don't show in the logs or in the source

    Description

    Child Processes don't show in the logs or in the source.

    Expected behavior:

    I would think I would be able to see my child processes kicked off by node app and put breakpoints in them. Also I would think I would see logs from them.

    Actual behavior:

    I can only see and interact with my main process.

    opened by jhicken 0
  • Error: Cannot find module, despite NODE_PATH being set

    Error: Cannot find module, despite NODE_PATH being set

    Description

    I use Typescript with a basePath setting, so that I can require my files from an absolute base path:

    import navigation from 'redux/interfaces/navigation'
    

    This gets transpiled to:

    const _navigation = require('redux/interfaces/navigator')
    

    The redux folder is in ./src/internal, so I have to set NODE_PATH accordingly.

    I want to use iron-node to debug my mocha unit test, which I can execute like this:

    NODE_PATH=./src/internal node node_modules/mocha/bin/_mocha --opts mocha.opts 'tests/**/*.spec.ts' 'tests/**/*.spec.tsx'
    

    This works, but if I replace node with iron-node, it cannot find the files in ./src/internal (see error log below)

    Steps to Reproduce

    I reproduced the issue with the following 2-file setup:

    1. Create file src/internal/redux/interfaces/navigation.js:
     module.exports = {
        a: true
    }
    
    1. Create file test/test.js:
    const _navigation = require('redux/interfaces/navigation')
    console.log(_navigation.a)
    
    1. Execute in shell (runs without errors): NODE_PATH=./src/internal node test/test.js
    2. Execute in shell (fails with module not found): NODE_PATH=./src/internal iron-node test/test.js

    Expected behavior: [What you expect to happen]

    iron-node should run without errors and find the required file.

    Actual behavior: [What actually happens]

    iron-node does not find the required file.

    Reproduces how often: [What percentage of the time does it reproduce?]

    Always.

    Screenshot(s): [Screenshot(s) or animated gifs of the error situtaion]

    Error log(s): From devTools console or shell terminal

    app.js:197 ironNode boot
    /usr/lib/node_modules/iron-node/app/require-custom-wrap.js:32 Object {v8: Object, app: Object, workSpaceDirectory: function}
    app.js:268 ModedModule {}
    app.js:58   Error: Cannot find module 'redux/interfaces/navigation'
      
      - reset-search-paths.js:35 Function.Module._resolveFilename
        [lib]/[iron-node]/[electron]/dist/resources/electron.asar/common/reset-searc    h-paths.js:35:12
      
      - module.js:20 require
        internal/module.js:20:19
      
      - test.js:1 Object.<anonymous>
        /tmp/test-project/test/test.js:1:176
      
      - test.js:3 Object.<anonymous>
        /tmp/test-project/test/test.js:3:3
      
    
    error @ app.js:58
    emitOne @ events.js:96
    emit @ events.js:191
    window.onerror @ /usr/lib/node_modules/iron-node/node_modules/electron/dist/resources/electron.asar/renderer/init.js:135
    app.js:59 Details Error: Cannot find module 'redux/interfaces/navigation'
        at Module._resolveFilename (module.js:470)
        at Function.Module._resolveFilename (/usr/lib/node_modules/iron-node/node_modules/electron/dist/resources/electron.asar/common/reset-sea…:35)
        at Function.Module._load (module.js:418)
        at Module.require (module.js:498)
        at require (internal/module.js:20)
        at Object.<anonymous> (/tmp/test-project/test/test.js:1)
        at Object.<anonymous> (/tmp/test-project/test/test.js:3)
        at Module._compile (module.js:571)
        at Object.Module._extensions..js (module.js:580)
        at Module.load (module.js:488)
    error @ app.js:59
    emitOne @ events.js:96
    emit @ events.js:191
    window.onerror @ /usr/lib/node_modules/iron-node/node_modules/electron/dist/resources/electron.asar/renderer/init.js:135
    

    Version(s)

    versions

    opened by janstrohbeck 0
Releases(v3.0.18)
Owner
Stephan Ahlf
Chuck Norris doesn't use GUI, he prefers COMMAND line.
Stephan Ahlf
📡 Encrypt and authenticate DevTools to use it securely remotely. Add HTTPS, and authentication to --remote-debugging-port to debug, inspect and automate from anywhere and collaborate securely on bugs.

?? Encrypt and authenticate DevTools to use it securely remotely. Add HTTPS, and authentication to --remote-debugging-port to debug, inspect and automate from anywhere and collaborate securely on bugs.

Cris 9 May 5, 2022
ndb is an improved debugging experience for Node.js, enabled by Chrome DevTools

ndb ndb is an improved debugging experience for Node.js, enabled by Chrome DevTools Installation Compatibility: ndb requires Node >=8.0.0. It works be

null 10.8k Dec 28, 2022
Streamline Your Node.js Debugging Workflow with Chromium (Chrome, Edge, More) DevTools.

NiM (Node.js --inspector Manager) Streamlines your development process Google Chrome Web Store (works with any Chromium browsers: Google's Chrome, Mic

Will 188 Dec 28, 2022
thetool is a CLI tool to capture different cpu, memory and other profiles for your node app in Chrome DevTools friendly format

thetool thetool is a CLI tool to capture different cpu, memory and other profiles for your node app in Chrome DevTools friendly format. Quick start np

null 200 Oct 28, 2022
A tiny JavaScript debugging utility modelled after Node.js core's debugging technique. Works in Node.js and web browsers

debug A tiny JavaScript debugging utility modelled after Node.js core's debugging technique. Works in Node.js and web browsers. Installation $ npm ins

Sloth 10.5k Dec 30, 2022
Node is running but you don't know why? why-is-node-running is here to help you.

why-is-node-running Node is running but you don't know why? why-is-node-running is here to help you. Installation Node 8 and above: npm i why-is-node-

Mathias Buus 1.5k Dec 30, 2022
An lldb plugin for Node.js and V8, which enables inspection of JavaScript states for insights into Node.js processes and their core dumps.

Node.js v10.x+ C++ plugin for the LLDB debugger. The llnode plugin adds the ability to inspect JavaScript stack frames, objects, source code and more

Node.js 1k Dec 14, 2022
[OBSOLETE] runs Node.js programs through Chromium DevTools

devtool ⚠️ Update: This tool is mostly obsolete as much of the philosophy has been brought into Node/DevTool core, see here for details. If you wish t

Jam3 3.8k Dec 20, 2022
🐛 Memory leak testing for node.

Leakage - Memory Leak Testing for Node Write leakage tests using Mocha or another test runner of your choice. Does not only support spotting and fixin

Andy Wermke 1.6k Dec 28, 2022
Long stack traces for node.js inspired by https://github.com/tlrobinson/long-stack-traces

longjohn Long stack traces for node.js with configurable call trace length Inspiration I wrote this while trying to add long-stack-traces to my server

Matt Insler 815 Dec 23, 2022
API Observability. Trace API calls and Monitor API performance, health and usage statistics in Node.js Microservices.

swagger-stats | API Observability https://swaggerstats.io | Guide Trace API calls and Monitor API performance, health and usage statistics in Node.js

slana.tech 773 Jan 4, 2023
A Node.js tracing and instrumentation utility

njsTrace - Instrumentation and Tracing njstrace lets you easily instrument and trace you code, see all function calls, arguments, return values, as we

Yuval 354 Dec 29, 2022
Locus is a debugging module for node.js

ʆ Locus Locus is a debugging module which allows you to execute commands at runtime via a REPL. Installing npm install locus --save-dev Using require(

Ali Davut 300 Nov 13, 2022
He is like Batman, but for Node.js stack traces

Stackman 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

Thomas Watson 242 Jan 1, 2023
A professional truffle solidity template with all necessary libraries that support developer to develop, debug, test, deploy solidity smart contract

solidity-truffle-template A professional truffle solidity template with necessary libraries that support to develop, compile, test, deploy, upgrade, v

ChimGoKien 6 Nov 4, 2022
RWP stands for Roblox web panel, it's a code snippet that you can run via developer console or the provided Google Chrome extension to try out early

RWP stands for Roblox web panel, it's a code snippet that you can run via developer console or the provided Google Chrome extension to try out early Roblox site features before they're officially out without any programming experience.

null 10 Nov 28, 2022
Node.js debugger based on Blink Developer Tools

Node Inspector Overview Node Inspector is a debugger interface for Node.js applications that uses the Blink Developer Tools (formerly WebKit Web Inspe

null 12.6k Dec 29, 2022
Debug express.js server code with Ray to fix problems faster

express-ray Install this package in any Express.js project to provide an exceptional debugging experience using the Ray app by Spatie. Installation In

Permafrost Software 8 Nov 3, 2022
A GitHub Action that allows to debug GitHub workflows using VS Code.

VS Code Server Action A GitHub Action that allows to debug GitHub workflows using VS Code. Failing CI builds can be annoying especially since we don't

stateful 18 Dec 23, 2022
📡 Encrypt and authenticate DevTools to use it securely remotely. Add HTTPS, and authentication to --remote-debugging-port to debug, inspect and automate from anywhere and collaborate securely on bugs.

?? Encrypt and authenticate DevTools to use it securely remotely. Add HTTPS, and authentication to --remote-debugging-port to debug, inspect and automate from anywhere and collaborate securely on bugs.

Cris 9 May 5, 2022