Skip to content

v6.x.x / v7.0.0 - wish list / roadmap #563

Closed
@yoshuawuyts

Description

@yoshuawuyts

I want to gather a bit of sentiment for what people might be missing / what you feel might improve. The same as in v6, it'd be nice if all that was needed to update the major was npm install --save choo@7, and that's it.

So far my wish list is:

  • Figure out how to make routes render async, so we can apply route-based code splitting when needed. Not necessarily breaking, but it might just turn out that we need to rewrite the router (again, sigh - haha).
  • Remove the unique labels from the tracing API measures, there's no need for them when using a PerformanceObserver like in choo-log.
  • Replace xtend with Object.assign() - https://polyfill.io provides a fallback for browsers that don't support it, so for most people this will be a strict improvement.
  • choo/component, using nanocomponent - Ideally it'd be nice if we could formalize tracing / an event system with this too. That way we keep blazing ahead in terms of debugging.
  • Reading out from a global state (e.g. window.initialState) to provide out of the box "rehydration" of state that was passed on the server.

It's still early, but I'd be interested in hearing input from people on what you find tricky, which things you love, and which things you struggle with! Thanks! ✨

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions