All Versions
Latest Version
Avg Release Cycle
62 days
Latest Release
1161 days ago

Changelog History
Page 1

  • v7.1.0

    January 23, 2020
  • v7.0.0 Changes

    June 12, 2019

    It has been quite a while since the last major version of Choo. Since it's πŸš€ release, [email protected] has recieved a bunch of features and patches, but some changes has been put off because they'd have an affect on the API in a way that could be πŸ’₯ breaking for some users. With this release we've merged all these minor, but πŸ’₯ breaking changes all at once.

    The way in which Choo handles hashes in the URL has proved confusing for both πŸ†• newcomers and seasoned Choo users. In a prior patch the hash option was added πŸš€ which could be used to disable hash routing. With this release we're changing it 0️⃣ to be disabled by default.

    🐎 Rendering pages server side is an excellent way to increase page performance and πŸ‘ Choo supports it out of the box. Choo also allows for rehydrating the client with what state was used when rendering on the server side. To ensure that the application state is identicial regardless if hydrated or not, the internals for routing has been changes so that href, query, param and route are all available on application state at the time when stores are initialized.

    In prior versions, when rendering on the server, the state that was provided to πŸ”€ toString would be merged onto the application state. Meaning consecutive calls to toString would accumulate on the application state and persist in-between render. With this change, application state is no longer mutated during server side render. This will affects those of you doing server side rendering and then plucking out properties from the application state. You can now be assured that only the state that is provided to toString is modified during rendering.

    var html = app.toString('/', state)
    - var title = app.state.title
    + var title = state.title

    ⚑️ And lastly, we've updated depndencies and even dropped a dependency which is πŸ’» no longer required by modern browsers. The dependency xtend was dropped in favour of 🌐 Object.assign. This change has also been propagated throughout πŸ‘· the Choo universe i.e. choo-devtools and choo-service-worker etc. If you are πŸ‘Œ supporting legacy browsers (IE11 and bellow), we recommend the polyfill service πŸ’» which will detect legacy browsers and load the appropiate polyfills.

    That's all for now, keep being awesome!

  • v7.0.0-0 Changes

    June 12, 2019


    $ npm install [email protected]

    0️⃣ Hash routing has been disabled by default (#699)

    0️⃣ Hashes are by default ignored when routing. To enable hash routing, set the hash option to true choo({ hash: true }).

    Match route before intializing stores (#698)

    This means that href, query, param and route are exposed on state before stores are initialized. This can be usefull while setting up the initial state.

    State is not mutated during server side render (#649)

    Prior to this change, when calling toString, changes to state would persist in-between renders. This could lead to a polluted state. This change also clears all event listeners before initializing stores, meaning your listeners are ensured to only trigger once, even on consecutive calls of toString.

    ⚑️ If you were doing server side rendering prior to this update, you were probably plucking at the application state after rendering to get at the generated state. You can now be assured that it is only the state that is passed in to toString that is mutated and can e.g. be used to expose initialState to the client.

    var html = app.toString('/', state)- var title = app.state.title+ var title = state.title

    πŸ‘‰ Use Object.assign instead of xtend (#616)

    πŸ’» This change has an effect on browser support. By removing the dependency xtend, bundle size is reduced but support for IE11 is dropped. We recommend the polyfill service which will detect legacy browsers and load the appropiate polyfills.

    Note: The dependency xtend has been dropped in all other tools in the choo universe, i.e. choo-devtools and choo-service-worker etc.

  • v6.13.3 Changes

    April 23, 2019
    • βͺ Revert changes to store init order
  • v6.13.2 Changes

    April 02, 2019
    • πŸ›  Fix href, query, route and params missing on state during store init (#695)
  • v6.13.1 Changes

    October 30, 2018
  • v6.13.0 Changes

    July 12, 2018

    πŸ”„ Changes

    • βž• Added documentation on components
    • βž• Added hash option for disabling hash routing

    Related Pull Requests

  • v6.12.1 Changes

    June 13, 2018

    πŸ“¦ Republishing to npm to remove unrelated files that were accidentally included in the package.

  • v6.12.0 Changes

    June 13, 2018

    πŸš€ The πŸ’―th release tag!

  • v6.11.0 Changes

    May 22, 2018