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

@beequeue/esbuild-plugin-file-path-extensions

v2.1.0

Published

An esbuild plugin to automatically insert file extensions in your built JavaScript files based on the specified target

Downloads

5

Readme

esbuild-plugin-file-path-extensions

An esbuild plugin to automatically insert file extensions in your built JavaScript files based on the specified target

GitHub npm

Table of Contents

Description

In order to properly and fully support packaging your code for both CJS and ESM when using esbuild you will want to ensure that all your imports and exports are using their respective file extensions (i.e. .js for CJS and .mjs for ESM) to ensure that NodeJS can always load the appropriate files when they are within the same folder. However, managing this manually is an absolute nightmare and annoyance to do in the source code. This plugin alleviates that issue by automatically appending the file path extensions when building the code.

Installation

You can use the following command to install this package, or replace npm install -D with your package manager of choice.

npm install -D esbuild-plugin-file-path-extensions

Usage

Warning When using this plugin you HAVE to set the bundle option to true for file paths to be resolved correctly. Do note however then when doing this your code will NOT bundle all into 1 file. An example of where this plugin is used and what the output will be after it is used can be found at sapphiredev/framework

Note If you import a file and append a file one of the file extensions js, cjs, mjs, ts, cts, or mts then this plugin will skip that import and use the originally provided extension. This is to ensure that no double file extensions are added.

With esbuild

Add the plugin to your esbuild options, i.e.:

const esbuild = require('esbuild');
const { resolve } = require('path');
const {
  esbuildPluginFilePathExtensions
} = require('esbuild-plugin-file-path-extensions');

await esbuild.build({
  format: 'cjs',
  entryPoints: [resolve(__dirname, './src/index.ts')],
  outdir: resolve(__dirname, './dist'),
  bundle: true,
  plugins: [esbuildPluginFilePathExtensions()]
});

With tsup

Add the plugin to your tsup.config.ts, i.e.:

import { defineConfig } from 'tsup';
import { resolve } from 'path';
import { esbuildPluginFilePathExtensions } from 'esbuild-plugin-file-path-extensions';

await defineConfig({
  format: ['cjs', 'esm'],
  entry: ['src/**/*.ts'],
  outDir: './dist',
  bundle: true,
  esbuildPlugins: [esbuildPluginFilePathExtensions()]
});

Options

The plugin accepts the following options:

  • esm: Boolean, whether the current build is for ESM or not. Defaults to build.initialOptions?.define?.TSUP_FORMAT === '"esm"' in order to account for the cross-target capabilities of tsup.

  • cjsExtension: The extension to apply for CJS code. Defaults to js. Make sure to NOT start with a leading ..

  • esmExtension: The extension to apply for ESM code. Defaults to mjs. Make sure to NOT start with a leading ..

  • filter: This is an advanced use-case option with which you can filter which files esbuild should apply this plugin on

  • namespace: This is an advanced use-case option through which the esbuild namespace can be configured

Buy us some doughnuts

Favware projects are and always will be open source, even if we don't get donations. That being said, we know there are amazing people who may still want to donate just to show their appreciation. Thank you very much in advance!

We accept donations through Ko-fi, Paypal, Patreon, GitHub Sponsorships, and various cryptocurrencies. You can use the buttons below to donate through your method of choice.

| Donate With | Address | | :-------------: | :-----------------------------------------------: | | Ko-fi | Click Here | | Patreon | Click Here | | PayPal | Click Here | | GitHub Sponsors | Click Here | | Bitcoin | 1E643TNif2MTh75rugepmXuq35Tck4TnE5 | | Ethereum | 0xF653F666903cd8739030D2721bF01095896F5D6E | | LiteCoin | LZHvBkaJqKJRa8N7Dyu41Jd1PDBAofCik6 |

Contributors

Please make sure to read the Contributing Guide before making a pull request.

Thank you to all the people who already contributed!