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 🙏

© 2026 – Pkg Stats / Ryan Hefner

use-contao-next

v0.2.6

Published

React hook for using a Contao Backend inside next.js with the Contao Content API

Readme

use-contao-next

This package provides an example implementation using React Hooks inside Next.js.

Requirements

A valid contao installation with the Contao Content API extension installed.

Using next.js the Contao API can be fetched on build time, when rendering on server (SSR) or even on the client side (CSR). See the example implementation for more details.

Further goals

Currently the hooks are extended with data models and dynamic resolving of pages using slugs. Further a dynamic binding shall be implemented to assign different Contao Content Elements to JSX Components.

Example

Live Example

Using example

The example requires an existing installation of Contao 4.4+ and the Contao Content API. You can install the Contao Content API by using the Contao Manager or the composer CLI:

composer require dieschittigs/contao-content-api

To build the example, run

npm run build

Then the example can be started using

cd example && npm run start

When building the example the resulting pages will be:

Page                                                           Size     First Load
┌ ○ /                                                          1.83 kB     80.8 kB
├   /_app                                                      11.2 kB       79 kB
├ ○ /404                                                       3.15 kB     82.1 kB
├ ○ /csr                                                       451 B       84.6 kB
├ ○ /csr/another                                               457 B       84.6 kB
├ ○ /csr/context                                               419 B       84.5 kB
├ ○ /csr/context/another                                       425 B       84.5 kB
├ λ /page/[...slug]                                            343 B       79.3 kB
├ λ /ssr                                                       416 B       84.5 kB
├ λ /ssr/another                                               500 B       84.6 kB
├ ● /static                                                    393 B       84.5 kB
└ ● /static/another                                            397 B       84.5 kB

λ  (Lambda)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
○  (Static)  automatically rendered as static HTML (uses no initial props)
●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)