Nanohtml#109
Conversation
|
re the license change choojs/choo#582 (comment) |
|
Reverted to MIT |
|
Ported benchmarks. Depends on mafintosh/nanobench#7 to be merged, but it shouldn't hold up merging this I reckon. Thanks! |
| ### Browserify | ||
| ```sh | ||
| $ browserify -t nanohtml index.js > bundle.js | ||
| ``` |
| "main": "index.js", | ||
| "browser": "browser.js", | ||
| "name": "nanohtml", | ||
| "description": "HTML template strings renderer for Node & Browsers.", |
There was a problem hiding this comment.
HTML template string renderer for the browser & Node
i think we should display preference towards the browser here
| @@ -0,0 +1,4 @@ | |||
| declare module "bel" { | |||
|
@oe updated with all feedback! |
|
Damn.. Is |
|
I thiiink Bel 6 is the same as Bel 5 but with a deprecation notice on npm. Not 100% sure, am on mobile!
…On 14 March 2018 18:47:54 CET, Charlike Mike Reagent ***@***.***> wrote:
Damn.. Is `bel` 6 same as this? Why not just created `nanohtml` and let
`bel` as it was on latest v5? Now updating services may update to v6 -
it won't be a problem cuz is drop in replacement, but will pull more
dependencies... Another way is to ignore the v6 update. ;/ Really sad.
Bel worked both sides anyway.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#109 (comment)
--
Sent from mobile. Please excuse my brevity.
|
|
That would be good if so. |
|
@olstenlarck yep, @goto-bus-stop is right - that's exactly what we did. Most so if people perform a fresh |
Changes
belintonanohtml. The main goal here is to mergebel,yoyoifyandpelointo a single module that does all of these things. This should make it easier to maintain, test and point people to the right modules. Thanks!Tasks
Fixes #33