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

wexts-netlify-plugin

v1.0.0

Published

Netlify Build Plugin for WEXTS framework projects

Readme

@wexts/netlify-plugin

📖 View Full Documentation

Official Netlify Build Plugin for WEXTS framework projects.

Installation

Automatic (Recommended)

The plugin will be automatically installed when Netlify detects a WEXTS project.

Manual Installation

Add to your netlify.toml:

[[plugins]]
package = "@wexts/netlify-plugin"

Or install via npm:

pnpm add -D @wexts/netlify-plugin

Configuration

Basic Setup

Create a netlify.toml in your project root:

[build]
  command = "pnpm run build"
  publish = "apps/web/.next"

[[plugins]]
package = "@wexts/netlify-plugin"

Advanced Configuration

Override default settings:

[[plugins]]
package = "@wexts/netlify-plugin"

  [plugins.inputs]
  frontendDir = "apps/web"
  backendDir = "apps/api"
  buildCommand = "turbo run build"
  publishDir = "apps/web/.next"

Features

  • ✅ Automatic WEXTS project detection
  • ✅ Monorepo support (Turborepo, pnpm workspace)
  • ✅ Next.js frontend optimization
  • ✅ NestJS serverless functions support
  • ✅ Build caching for faster deployments
  • ✅ Helpful error messages

How It Works

  1. onPreBuild: Detects WEXTS project and restores cache
  2. onBuild: Builds frontend and backend
  3. onPostBuild: Saves cache for next deployment
  4. onSuccess: Shows deployment summary
  5. onError: Provides debugging information

WEXTS Configuration

If you have a wexts.config.ts, the plugin will automatically use it:

import { WextsConfig } from '@wexts/config';

const config: WextsConfig = {
  framework: 'wexts',
  version: '2.0.0',
  apps: {
    frontend: {
      dir: 'apps/web',
      framework: 'nextjs'
    },
    backend: {
      dir: 'apps/api',
      framework: 'nestjs'
    }
  },
  monorepo: {
    tool: 'turborepo'
  }
};

export default config;

Environment Variables

Set these in your Netlify dashboard if needed:

  • NODE_VERSION: Node.js version (default: 18)
  • PNPM_VERSION: pnpm version (default: latest)

Deploying

Via Git

  1. Connect your repository to Netlify
  2. Netlify will auto-detect the plugin
  3. Deploy!

Via CLI

netlify deploy

Troubleshooting

Build fails with "Module not found"

Make sure all dependencies are in package.json's dependencies, not devDependencies.

Frontend not deploying

Check that publishDir points to the correct build output (usually .next for Next.js).

Backend functions not working

Ensure your NestJS routes are compatible with Netlify Functions format.

License

MIT