npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@drewschrauf/rerouter

v0.0.1

Published

Rerouter is a minimal router for [ReasonReact](https://reasonml.github.io/reason-react/) projects. It uses [history](https://github.com/ReactTraining/history) under the hood to make testing simple.

Downloads

2

Readme

Rerouter

Rerouter is a minimal router for ReasonReact projects. It uses history under the hood to make testing simple.

Wait, doesn't ReasonReact have a built-in router?

Yes! An excellent one, in fact.

However, its strength is also its weakness. It provides very thin bindings to the browser's API for reading and updating the URL. Unfortunately, these APIs are not supported by Jest (and, by extension, @glennsl/bs-jest).

This router makes use of history to enable the use of the browser history in the browser and an in-memory history for testing.

Installation

Just install the package

yarn add @drewschrauf/rerouter

and add it to your bsconfig.json

{
    ...,
    "bs-dependencies": {
    	...,
    	"@drewschrauf/rerouter"
	}
}

Usage

Simply wrap the <Rerouter /> component around your application and you're good to go.

/* Index.re */
ReactDOMRe.renderToElementWithId(<Rerouter> <App /> </Rerouter>)

Within your app you can make use of useUrl() and useHistory() to get your current location and update it respectively.

When you're writing your tests (ideally with @glennsl/bs-jest and @drewschrauf/react-testing-library), render your app inside a <Rerouter /> component with a memory history instead.

/* MyTest_test.re */
test("app should render", () => {
	let history = Rerouter.History.createMemoryHistory(~initialEntries=["/"], ());
	render(<Rerouter history> <App /> </Rerouter>);
})

API

The API is heavily based on ReasonReactRouter. It's worth giving their own documentation a read to see why this approach to a React router is so perfect for Reason.

Context and Hooks

<Rerouter history=option(Rerouter.History.t) />

The history context provider. The must be wrapped around your application in order to be able to use the following hooks. If no history is passed, a browser history is instantiated and used.

useUrl(): { path: list(string), search: string, hash: string }

Retrieves the current URL parts. The API is identical to that provided by ReasonReactRouter.

useHistory(): Rerouter.History.t

Retrieves the history object. This is required for passing to the push and replace methods below.

History

createBrowserHistory(~basename: string=?, ~forceRefresh: bool=?, ~keyLength: int=?, ()): Rerouter.History.t

Create a history object for use within the browser. You usually won't need to call this yourself unless you want to customise the instance. Using <Rerouter /> without a history argument will instantiate one of these by default.

createMemoryHistory(~initialEntries: list(string)=?, ~initialIndex: int=?, ~keyLength: int=?, ()): Rerouter.History.t

Create a history object for use in tests. Pass this as the history prop of your <Rerouter /> context provider.

push(history: Rerouter.History.t, url: string): unit

Navigate to the given URL.

replace(history: Rerouter.History.t, url: string): unit

Navigate to the given URL, replacing the current URL in the history.