Vincent Weevers
Vincent Weevers
I've seen and written code examples in READMEs that are not 100% correct, for example to quickly demonstrate two ways to achieve the same thing: ```js const x = doItOneWay()...
You wouldn't be able to use the full range of bytes, as two must be reserved for separator and `lt` logic. Limiting the prefix to ASCII characters makes that easier...
Sure, it's possible, at the cost of complexity. Can you explain your use case? I'm curious about the benefit of buffer prefixes, if you can't use the full range of...
Wouldn't escaping hurt the ability to use it as an index?
Can you share some code to clarify the use case?
That's reasonable. Would only require work in the constructor. Slightly easier to achieve in `abstract-level` because its `db.sublevel()` method has less overloads. There it could look like `db.sublevel(['foo', bar'])` as...
> I was also wondering why it requires `await` It doesn't. Can you share a snippet of code where you need `await`?
> It would preferable that subleveldown matches the API of level On that point: https://github.com/Level/abstract-level
```yaml browserify: - transform: babelify presets: ['@babel/preset-env'] plugins: ['@babel/plugin-syntax-import-assertions'] ```
My example was just to show how to specify transform options. The complete configuration should also include esmify.