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

page-lifecycle-provider

v1.1.2

Published

The page lifecycle provider introduces a concept of page lifecycles to route changes. The useful scenario is to raise an event when navigations happen (easy using react-router already), then raise another event once all the data has been loaded for that r

Downloads

148

Readme

Page LifeCycle Provider

The page lifecycle provider introduces a concept of page lifecycles to route changes. The useful scenario is to raise an event when navigations happen (easy using react-router already), then raise another event once all the data has been loaded for that route (harder).

Usage

Render PageLifecycleProvider between React-Router Router and the routes of your application.

const App: React.SFC<{}> = () => (
    <BrowserRouter>
        <PageLifecycleProvider onEvent={(event) => { console.log(event) }}
            <Main />
        </PageLifecycleProvider>
    </BrowserRouter>
)

onEvent will then raise page-load-started and page-load-complete events.

Data Loading

Add loading and loaded props to your component which loads data

const ComponentWhichLoadsData = () => {
    const pageProps = React.useContext(PagePropertiesContext)

    const [data, setData] = React.useState()

    React.useEffect(() => {
        pageProps.beginLoadingData()
        getData().then(loadedData => {
            setData(loadedData)
            pageProps.endLoadingData()
        })
    })

    return data ? <RenderData data={data}> : 'Loading...'
}

The PageLifecycleProvider also can be used instead of the context if you have a way to globally know when data is being loaded.

const App = () => (
    <BrowserRouter>
        <PageLifecycleProvider>
            {({ beginLoadingData, endLoadingData }) => (
                <DataLoader
                    onBeginLoadData={beginLoadingData}
                    onEndLoadData={endLoadingData}
                >
                    <Main />
                </DataLoader>
            )}
        </PageLifecycleProvider>
    </BrowserRouter>
)

Adding properties to the payload

Often you want extra data in your events, you can do this with the PageProps component

const ComponentWhichLoadsData = () => {
    const pageProps = React.useContext(PagePropertiesContext)

    const [data, setData] = React.useState()

    React.useEffect(() => {
        pageProps.beginLoadingData()
        getData().then(loadedData => {
            setData(loadedData)
            pageProps.endLoadingData()
        })
    })

    return data ? <PageProps pageProperties={{ extra: 'value' }}><RenderData data={data}></PageProps> : 'Loading...'
}

Now the events will have { payload: { extra: 'value' }}. Multiple page props will be merged together.

API

PageEvents

Page events are:

export interface PageLoadStarted {
    type: 'page-load-started'
    timeStamp: number
    originator: string
    payload: {
        [key: string]: any
    }
}

export interface PageLoadFailed {
    type: 'page-load-failed'
    timeStamp: number
    originator: string
    payload: {
        error: string
        [key: string]: any
    }
}

export interface PageLoadComplete {
    type: 'page-load-complete'
    timeStamp: number
    originator: string
    payload: {
        [key: string]: any
    }
}