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

@locator/webpack-loader

v0.5.1

Published

Webpack/Turbopack loader for LocatorJS that enables component location tracking in projects using SWC or Turbopack where direct Babel plugin usage is not possible.

Downloads

28,872

Readme

@locator/webpack-loader

Webpack/Turbopack loader for LocatorJS that enables component location tracking in projects using SWC or Turbopack where direct Babel plugin usage is not possible.

Works with both Webpack and Turbopack (Next.js 15+).

Installation

npm install --save-dev @locator/webpack-loader
# or
yarn add -D @locator/webpack-loader
# or
pnpm add -D @locator/webpack-loader

Usage

Next.js 15+ with Turbopack

Add this to your next.config.ts or next.config.js:

import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  turbopack: {
    rules: {
      "**/*.{tsx,jsx}": {
        loaders: [
          {
            loader: "@locator/webpack-loader",
            options: {
              env: "development",
            },
          },
        ],
      },
    },
  },
};

export default nextConfig;

Next.js with Webpack (or with SWC)

Add this to your next.config.js:

module.exports = {
  webpack: (config, { isServer }) => {
    if (!isServer) {
      config.module.rules.push({
        test: /\.(tsx|ts|jsx|js)$/,
        exclude: /node_modules/,
        use: [
          {
            loader: "@locator/webpack-loader",
            options: {
              env: "development",
            },
          },
        ],
      });
    }
    return config;
  },
};

Generic Webpack Configuration

module.exports = {
  module: {
    rules: [
      {
        test: /\.(tsx|ts|jsx|js)$/,
        exclude: /node_modules/,
        use: [
          {
            loader: "@locator/webpack-loader",
            options: {
              env: "development",
              ignoreComponentNames: ["CustomProvider"], // optional
            },
          },
        ],
      },
    ],
  },
};

Options

  • env (string, optional): Environment to run the loader in. Defaults to process.env.NODE_ENV or "development".
  • ignoreComponentNames (string[], optional): Array of component names to ignore during transformation.

How It Works

This loader uses Babel's transform API to apply the @locator/babel-jsx plugin to your JSX/TSX files. It adds data-locatorjs attributes with full file path and location information to your components, enabling click-to-source functionality even in React Server Components where JavaScript execution is limited.

The loader:

  1. Parses your JSX/TSX files using Babel
  2. Applies the LocatorJS transformation with path-based attributes (data-locatorjs="/path/to/file.tsx:line:column")
  3. Returns the transformed code with sourcemaps
  4. Automatically skips node_modules and middleware files
  5. Works without requiring window.__LOCATOR_DATA__ - perfect for Server Components

Requirements

  • Webpack 5.x
  • Works with React, Preact, and SolidJS

Related Packages

More Information

Visit locatorjs.com for complete documentation and installation guides.