You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More generally, since --node is still being run through browserify, it has a few other limitations like module.filename. It would be better if --node were to just use Electron's node integration directly, however this has a lot of other implications like:
we would need to maintain our own file watcher that handles module dependencies
no support for browser transforms like glslify / babelify / etc
can't take advantage of 'browser' field resolution
With all this in mind, it seems a bit out of scope for a (primarily browser-based) tool like hihat.
The text was updated successfully, but these errors were encountered:
What is your use case? I think for typical node source it would be better to avoid browserify altogether. I'm exploring some ways of abstracting Hihat into more general purpose modules for this use case.
require.resolve
does not work withhihat --node
(related: browserify/browserify#1340)
More generally, since
--node
is still being run through browserify, it has a few other limitations likemodule.filename
. It would be better if--node
were to just use Electron's node integration directly, however this has a lot of other implications like:'browser'
field resolutionWith all this in mind, it seems a bit out of scope for a (primarily browser-based) tool like
hihat
.The text was updated successfully, but these errors were encountered: