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

next-public

v0.5.0

Published

A webpack plugin to compile TypeScript files in the public folder of a Next.js project.

Downloads

370

Readme

next-public

A webpack plugin to compile TypeScript files in the public folder of a Next.js project.
I created this Webpack plugin because I wanted to use TypeScript in the public folder of my Next.js project but Next.js doesn't support this out of the box.

Features

  • Write your Service Workers and your Web Workers in TypeScript
  • Handle process.env.NEXT_PUBLIC_* in your TypeScript files
  • Compile and minify your TypeScript files
  • Detect files to compile with autoDetect option and +public directory
  • Inject a SHA-1 hash of the file content into %checksum% variable in the compiled file
  • Support for CommonJS and ES modules

Installation

npm install --save-dev next-public

Usage

Auto-detect *.ts files with +public directory

// next.config.js
const { NextPublicTsPlugin } = require("next-public");

const nextConfig = {
  webpack(config, context) {
    config.plugins.push(
      new NextPublicTsPlugin({
        autoDetect: true,
      }),
    );
    return config;
  },
};

With inputDir and outputDir options

// next.config.mjs
import path from "node:path";
import { NextPublicTsPlugin } from "next-public";

/**
 * @type {import('next').NextConfig}
 */
const nextConfig = {
  webpack(config, context) {
    config.plugins.push(
      new NextPublicTsPlugin({
        inputDir: path.join("src", "app", "+public"),
        outputDir: path.join("public"),
      }),
    );
    return config;
  },
};

export default nextConfig;

Examples

You can find examples in the examples directory.

Plugin options

  • enabled : A boolean value indicating whether the plugin should be enabled. Defaults to true.
    NOTE : Use this option to disable the plugin in development mode.

  • autoDetect : A boolean value indicating whether the plugin should automatically detect the TypeScript files in the input directory. Defaults to false.
    e.g. : If you want to let the plugin to detect TypeScript files in app/+public directory.

  • inputDir : A string representing the path to the directory containing the TypeScript files to be compiled.

  • outputDir : A string representing the path to the directory where the compiled JavaScript files will be written.