v6 beta branch

[yoshuawuyts]

in-progress target branch we can use for breaking behavior. The prototype branch is basically a full rewrite; this allows us to put out some betas and iterate on the minor changes we want for the next version.

Basically I'm thinking we keep the API stable, but yeah there's a few nits that are technically breaking. So we should iron those out in a semver major. Yay for boring changes ✨

related issues

• call DOMcontentloaded on next frame call DOMContentLoaded on next frame #465
• use nanotiming use nanotiming #476
• become prototype based become prototype based #480
• add tracing to nanobus add nanotiming nanobus#10
• revert special casing of root onload handlers Revert on-load attribute special case behaviour nanomorph#65
• fix select tags fix for node type select and add tests for select nodes nanomorph#60
• remove onload remove onload nanohtml#69
• should clear performance timers choo should clear performance timers #461
• remove nanomount Remove nanomount #481
• remove nanohistory (too small a module)
• fix whitespace in bel
• fix whitespace in yo-yoify add whitespace collapse for bel 5 parity shama/yo-yoify#49
• fix whitespace in pelo Clean up whitespace shuhei/pelo#7
• upgrading bankai to new yo-yoify
• upgrading bel to new pelo

[yoshuawuyts]

Timing API has been upgraded, now shows separate timings for creating DOM trees + morphing the trees.

I'm not sure about the event names tho; right now they are:

choo.render:view.route   # for choo's internal stuff
choo.emitter:foo:bar     # for an event a user registers

What I'm wondering is if we should perhaps upgrade nanobus to delimit internal events with a "/" so it'd become:

choo:render/view:route   # for choo's internal stuff
choo:emitter/foo:bar     # for an event a user registers

Thoughts? cc/ @juliangruber @timwis

[yoshuawuyts]

note to self: move the new choo performance.measure() to requestIdleCallback and use choojs/nanotiming#1

[juliangruber]

thoughts:

• [choo] render: view.route
• choo.render(view.route)
• [choo] render(view.route)

[moszeed]

i like the following proposals by @juliangruber

• choo.render(view.route)
• [choo] render(view.route)

[yoshuawuyts]

@juliangruber gonna try some of those out; like the choo.render(view.route) idea for sure! - should become part of choojs/nanotiming#3 I reckon

edit: The syntax to create timings internally is:

var nanotiming = require('nanotiming')
var nanobus = require('nanobus')

var timing = nanotiming('choo')
var uuid = timing.start('render')
timing.end(uuid, 'render')

var timing = nanotiming('choo')
var name = "route['" + '/' + "']"
var uuid = timing.start(name)
timing.end(uuid, name)

var emitter = nanobus('choo.emit')
emitter.emit('log:debug')

So this leaves us somewhat constrained in our display options. I'm thinking naming like this might be neat:

choo(render) [12356778]
choo(route['/']) [13355671]
choo.emit('log:debug') [13355675]

The weird tailing numbers are unique UUIDs because turns out we need them if we wanna keep tracing stuff. The output for choo-log can be modified by updating the Nanobus package. I def like this better than what we have now (:

[yoshuawuyts]

Also thinking of adding a navigate event which is fired whenever path changes, and returns the current name of the route. This could be used in the logger as a debug style event - and would be useful for APM providers so they can hook into the actual name of the route.

edit: also expose the route name as state.route

[tornqvist]

Is there any reason for createLocation to not be exposed on the prototype? It would kind of solve #440 as you could roll your own method that ignores hashes and then simply set opts.href to false and implement nanohref in a similar way.

[yoshuawuyts]

@tornqvist I think what you're proposing makes sense (:

[yoshuawuyts]

Last issues remaining:

• add whitespace collapse for bel 5 parity shama/yo-yoify#49
• Clean up whitespace shuhei/pelo#7
• upgrading bankai to new yo-yoify
• upgrading bel to new pelo

[juliangruber]

three or two?

[yoshuawuyts]

Oops, good point - it's two brand new ones, and one that was introduced a
couple of weeks ago and folks might not be aware of. Will fix! :D

[yoshuawuyts]

Fixed!

[yoshuawuyts]

📦 v6.0.0-0 (release candidate)

Please share any feedback here #519. Thanks! 🎉