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

@knighted/module

v1.0.0-alpha.4

Published

Converts module differences in source files between ES and CommonJS.

Downloads

29

Readme

@knighted/module

CI codecov NPM version

Node.js utility for transforming a JavaScript or TypeScript file from an ES module to CommonJS, or vice versa.

  • ES module ➡️ CommonJS
  • CommonJS ➡️ ES module

By default @knighted/module transforms the one-to-one differences between ES modules and CommonJS, but it also accepts options that allow:

  • Converting import/export to require/exports
  • Extensions to be updated in relative specifiers
  • Write transformed source code to a filename

Requirements

  • Node >= 20.11.0

Example

Given an ES module

file.js

import { argv } from 'node:process'
import { pathToFileURL } from 'node:url'
import { realpath } from 'node:fs/promises'

const detectCalledFromCli = async path => {
  const realPath = await realpath(path)

  if (import.meta.url === pathToFileURL(realPath).href) {
    console.log('invoked directly by node')
  }
}

detectCalledFromCli(argv[1])

You can transform it to the equivalent CommonJS module

import { transform } from '@knighted/module'

await transform('./file.js', {
  type: 'commonjs'
  moduleLoading: true,
  out: './file.cjs'
})

Which produces

file.cjs

const { argv } = require('node:process')
const { pathToFileURL } = require('node:url')
const { realpath } = require('node:fs/promises')

const detectCalledFromCli = async path => {
  const realPath = await realpath(path)

  if (require('node:url').pathToFileURL(__filename).toString() === pathToFileURL(realPath).href) {
    console.log('invoked directly by node')
  }
}

detectCalledFromCli(argv[1])

When executed from the CLI

use@computer: $ node file.cjs
invoked directly by node

Options

type ModuleOptions = {
  /* What module system to convert to. */
  type?: 'module' | 'commonjs'
  /* Whether import/export and require/exports should be transformed. */
  modules?: boolean
  /* Whether to change specifier extensions to the assigned value. If omitted they are left alone. */
  specifier?: '.js' | '.mjs' | '.cjs' | '.ts' | '.mts' | '.cts'
  /* What filepath to write the transformed source to. */
  out?: string
}

Roadmap

  • Support option modules.
  • Remove @knighted/specifier and avoid double parsing.