v5.0.0-beta.4

You can track v5 beta progress in #751

You can install the v5 beta using the next tag: npm add history@next

Improvements from v5.0.0-beta.3:

• Export parsePath and createPath helper functions for dealing with paths
• Allow passing a string value to history.createHref
• Warn (instead of throw) in dev

A migration guide will be available soon. For now, you can either browse around the docs on the dev branch or the tests.

Enjoy!

v5.0.0-beta.3

You can track v5 beta progress in #751

You can install the v5 beta using the next tag: npm add history@next

Improvements from v5.0.0-beta.2:

• Added dev and prod builds for <script type=module> users

Now you can:

<script type="module">
import { createBrowserHistory } from 'https://unpkg.com/history@next/history.production.min.js';

let history = createBrowserHistory();

// And away you go!
</script>

A migration guide will be available soon. For now, you can either browse around the docs on the dev branch or the tests.

Enjoy!

v5.0.0-beta.2

You can track v5 beta progress in #751

You can install the v5 beta using the next tag: npm add history@next

Improvements from v5.0.0-beta.1:

• Individual bundles for each type of history: history/browser, history/hash, and history/memory
• Added singletons for browser and hash history
• Fixed some accidentally munged variable names in the production build

The singleton instances for browser and hash history are very convenient:

import history from 'history/browser';

// And away you go!

Unless we find any major bugs in this release, it will probably be the last beta before v5 final.

A migration guide will be available soon. For now, you can either browse around the docs on the dev branch or the tests.

Enjoy!

v5.0.0-beta.1

You can track v5 beta progress in #751

You can install the v5 beta using the next tag: npm add history@next

Improvements on v5.0.0-beta.0:

• Now using Closure Compiler which results in slightly smaller and faster builds
• New global UMD name window.HistoryLibrary does not conflict with window.History
• Adds sourcemaps

A migration guide will be available soon. For now, you can either browse around the docs on the dev branch or the tests.

Enjoy!

v5.0.0-beta.0

You can track v5 beta progress in #751

You can install the v5 beta using the next tag: npm add history@next

Lots of updates in this release! Here's a quick summary:

New features:

• Remove legacy browser support (pre pushState)
• Add state to hash history
• Use custom window when creating history objects
• Better history.block API w/ tx.retry for retrying transitions
• Fix location.pathname encoding issues
• About 50% smaller
• No dependencies

Removed features:

• Removes basename support
• Removes relative pathname support in hash + memory histories
• Removes getUserConfirmation
• Removes keyLength
• Removes hashType

A migration guide will be available soon. For now, you can either browse around the docs on the dev branch or the tests.

Enjoy!

v4.10.1

• Fixes some issues with using hash history on a page with a <base> tag (#577, #578)

v4.10.0

• Allows basename URL prefixes with special regex characters (#566, #544)

v4.9.0

The main change in this release is pre-bundled single-file builds for both development and production environments. This is not a breaking change, since we still support old-style require('history/createBrowserHistory') statements for now. However, these are deprecated in favor of importing/requireing from the main module.

Please see the release notes for 4.98.0-beta.0 for more info.

v4.8.0-beta.0

In 4.8.0 we will ship a single bundle for each module format (CJS, ESM, and UMD) using Rollup.

In this release we are deprecating support for

import createHistory from "history/createMemoryHistory";
// and
var createHistory = require('history/createMemoryHistory');

Instead, use:

import { createMemoryHistory as createHistory } from "history";
// and
var createHistory = require("history").createMemoryHistory;

together with a bundler that supports tree-shaking (Rollup or webpack 4 in production mode) to get your bundle sizes down.

Fixes

• Smaller builds, thanks to @TrySound (see #632 and #634)