Randall Leeds

The box where I have this issue is actually very memory constrained. I don't know if that's the cause but I suspect so. There's a fair bit of swapping during...

Any reason not to make that a distinct phase before deploy, though?

Yes. I should maybe refile this against dokku. But first we'd need to separate the start script and the chown so the latter can be executed separately, I think. On...

Not actively maintained, but I do occasionally find time at hackathons to work on this. I did some preliminary work on updating for a newer browserify at a meeting of...

It's very much known to me that this project doesn't work right now on anything beyond browserify v2. No need to test :).

I think what is needed is for the `getPlugins` call to pass `rootMode` as an option to the option manager initialization. Probably `rootMode: 'upward-optional'`. #101 properly sets the current working...

As far as I can tell from reading code, it seems as though this should already work if you specify a `root` option in the `import/resolver` `babel-module` settings to the...

I am mistaken. I had dug into this before and come to an earlier conclusion. I returned to try to make a PR and reached a different conclusion. I'm searching...

I've been able to solve this with a local workaround in my own project. Here are the relevant parts of my `.eslintrc.js`: ``` javascript const babel = require('@babel/core'); const babelOptions...

> Any idea why it falls to resolve in your project? I think the root cause is the `cwd` passed to `OptionsManager.prototype.init` in `getPlugins`. The `cwd` option passed is taken...