-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#249- only import 'level'
when it's actually used
#254
#249- only import 'level'
when it's actually used
#254
Conversation
335a7fa
to
d5a2b51
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Looks great over all, just a couple of comments.
i.e. if a developer provides their own `createLevelDatabase` then we will use that instead of `'level'` in order to support this for both node and browser, we need to switch to using dynamic `import` (instead of `require`, as that's not defined for node when `"type": "module"`) most of this commit is changing sync logic to `async` for that purpose (though it also allows for more flexibility when providing a custom `createLevelDatabase`)
d5a2b51
to
974c60a
Compare
@thehenrytsai can you publish an unstable version of this so @shamilovtim can consume? |
This one can probably just get merged. I need the unstable of the other PR and this rebased into that PR first |
@mistermoe and @shamilovtim, approved. Letting @dcrousso have the honor of merging. Feel free to merge if you can't wait. |
i.e. if a developer provides their own
createLevelDatabase
then we will use that instead of'level'
in order to support this for both node and browser, we need to switch to using dynamic
import
(instead ofrequire
, as that's not defined for node when"type": "module"
)most of this commit is changing sync logic to
async
for that purpose (though it also allows for more flexibility when providing a customcreateLevelDatabase
)