path.dirname(undefined) bug in v0.12.1

[MrBlenny]

In some versions of node/babel/webpack there are problems with path.dirname(undefined).

See here

path.dirname(undefined) will throw an error - as follows:

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.dirname (path.js:697:5)
    at Object.<anonymous> (C:\Users\david\repositories\stemn-electron\dist\main\index.js:11491:54)
    at __webpack_require__ (C:\Users\david\repositories\stemn-electron\dist\main\index.js:21:30)
    at Object.opt (C:\Users\david\repositories\stemn-electron\dist\main\index.js:11136:14)
    at __webpack_require__ (C:\Users\david\repositories\stemn-electron\dist\main\index.js:21:30)
    at Object.module.exports (C:\Users\david\repositories\stemn-electron\dist\main\index.js:10833:16)
    at __webpack_require__ (C:\Users\david\repositories\stemn-electron\dist\main\index.js:21:30)
    at Object.<anonymous> (C:\Users\david\repositories\stemn-electron\dist\main\index.js:10812:19)
    at __webpack_require__ (C:\Users\david\repositories\stemn-electron\dist\main\index.js:21:30)

Line 87 of lib/utils causes this problem for me in raven-node v0.12.1

var main_module = (require.main && path.dirname(require.main.filename) || process.cwd()) + '/';

This should be modified to become

var main_module = (require.main && require.main.filename && path.dirname(require.main.filename) || process.cwd()) + '/';

[LewisJEllis]

Cool, this sounds like a potential ready-to-go pull request; @MrBlenny do you want to create a PR with the change? I can also just apply the change you've described here if you'd like.

[MrBlenny]

I'm not actually sure how to create a PR for a specific release (as the code in master relates to the beta? not v0.12.1).

I created a copy of the repo @ v0.12.1 here that contains the change.

[LewisJEllis]

@MrBlenny published this in v0.12.2.