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

nuxt-typo3-config

v1.3.0

Published

Setup your nuxt-typo3 application with .env, .json or TYPO3 API.

Readme

Nuxt-TYPO3 configuration loader

Setup your nuxt-typo3 application with .env, .json or TYPO3 API.

Create .env file

Create your .env file

mkdir config
touch config/.env.stage

Run build with selected config file

It runs building process with .env.stage file

ENV_CONFIG=stage yarn build

Initial config

To configure TYPO3 multisites we can fetch initialConfig from TYPO3 API. You have to specify endpoint to get specific configuration:

.env.test:

#### NUXT-TYPO3 #######################################
#
# Connect to TYPO3 backend by API host
#
TYPO3_CONFIG_API=https://typo3instance.com/api?type=835
#
#######################################################

You can mockup initialConfig by json file - for example - env.test.json is the file for local environment.

{
    "typo3": {
      "domains": [
        {
          "name": "localhost",
          "baseURL": "https://www.mydomain.com",
          "api": {
            "baseURL": "https://api.mydomain.com"
          },
          "layouts": {
            "blank-page": "blank-page"
          },
          "i18n": {
            "defaultLocale": "uk"
          }
        }
  
      ]
    }
  }

Setup Nuxt app

loadConfiguration(config, dir)

Read .env files + .json with multidomains configuration

config - configuration key (for .env.production key will be "production", default: "production")

dir - your configuration directory (default: "config")

import loadConfiguration from 'nuxt-typo3-config'
const env = loadConfiguration()

export default {
    ...
    typo3: env.typo3
    ...
}

async getConfiguration(config, dir)

Read .env files and get configuration from API. To get configuration you have to specify TYPO3 endpoint by variable:

TYPO3_CONFIG_API=https://yourtypo3.com/?type=835

config - configuration key (for .env.production key will be "production", default: "production")

dir - your configuration directory (default: "config")

import { getConfiguration } from 'nuxt-typo3-config'

setupConfig = (env) => ({
    ...
    typo3: env.typo3
    ...
})

export default async () => {
  const env = await getConfiguration()

  return setupConfig(env)
}