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
My application is bundled for production use without node_modules installed. Currently classic-level looks for the binaries either in node_modules or in ./prebuilds (as far as I know). It would be nice to be able to specify a custom path upon initialization (e.g. as a config option).
The text was updated successfully, but these errors were encountered:
That's possible if we lazily require() the binding. But I'm not sure it's worth it, because an (IMO) reasonable workaround already exists (copying to ./node_modules/classic-level/prebuilds or to ./prebuilds). Either way the prebuilds have to live somewhere on disk, so why not there?
My application is bundled for production use without
node_modules
installed. Currentlyclassic-level
looks for the binaries either innode_modules
or in./prebuilds
(as far as I know). It would be nice to be able to specify a custom path upon initialization (e.g. as a config option).The text was updated successfully, but these errors were encountered: