Merge level and level-browserify
See original GitHub issueThe only difference is that level-browserify
has a browser.js
which pulls in level.js
. What do you think of merging them into one, e.g. deprecating level-browserify
and adding level.js
to level
?
It would mean less to maintain and also simple to use level
and it “just works”.
Upcoming version of level
will bundle levelup@2
, together with encoding-down
and have a promise layer as well, for people that prefer that.
- Release
level-browserify@2
first so we can get some testing
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:17 (14 by maintainers)
Top Results From Across the Web
level-browserify - npm
Fast & simple storage - a Node.js-style LevelDB wrapper (a convenience package bundling LevelUP & LevelDOWN or Level.js).
Read more >Using browserify and watchify to improve your client-side ...
I recommend adding package.json to the top-level folder of your ... As a final step, we can combine the output of browserify and...
Read more >Keep original typescript source maps after using browserify
Bottom line, I would like to merge the 2 js files but "merge" the js to ts source maps using browserify. Is that...
Read more >JavaScript Modules Part 2: Module Bundling - freeCodeCamp
On a high level, module bundling is simply the process of stitching ... Browserify is a tool that compiles CommonJS modules for the...
Read more >Prototype Pollution in browserify-shim | CVE-2022-37617 | Snyk
Unsafe Object recursive merge. The logic of a vulnerable recursive merge function follows the following high-level model: merge (target, source).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think we should release level
2.0.0
first. The work onlevel.js
will take a lot of time and we can release that as a minor once the new major is out.+1 in principle and +1 on adding it to the org. But yeah, it might take some work to get it up to par with
levelup@2
. Don’t underestimate that 😃