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

@codemanufacture/r.js

v3.0.0-alpha.2

Published

The idea is to ship the r.js distribution with the [espree](https://github.com/eslint/espree) parser instead of [esprima](https://github.com/jquery/esprima) which only supports up to ECMA2019.

Downloads

14

Readme

Purpose

The idea is to ship the r.js distribution with the espree parser instead of esprima which only supports up to ECMA2019.

Espree

Espree is a fork of Esprima, created by the ESLint team. It is designed to be fully compatible with Esprima's API and it is used as the default parser for ESLint.

Given r.js is a standalone script, we need to bundle espree with all of its dependencies so it can be added to the r.js build files, and ultimately to the r.js distro. Hence, we've added a commonjs version of espree, but wrapped as a requirejs module to r.js build folder.

This file is generated by cloning the espree repo and doing the following steps:

Install additional dev dependencies

npm install
npm install -D rollup-plugin-internal
npm install -D @rollup/plugin-node-resolve

Update the rollup configuration

The repo's rollup.config.js file expects the dependencies to be loaded via require, but we need to bundle them with the espree code. Update the config file as follows:

import commonjs from "@rollup/plugin-commonjs";
import resolve from "@rollup/plugin-node-resolve";
import json from "@rollup/plugin-json";
import internal from "rollup-plugin-internal";

export default {
    input: "espree.js",
    external: ["acorn", "acorn-jsx", "eslint-visitor-keys"],
    treeshake: false,
    output: {
        file: "dist/espree.cjs",
        format: "cjs"
    },
    plugins: [commonjs(), resolve(), json(), internal(['acorn', 'acorn-jsx', 'eslint-visitor-keys'])]
};

Run the build

npm run build

> [email protected] build
> rollup -c rollup.config.js


espree.js → dist/espree.cjs...
created dist/espree.cjs in 636ms

Rename and wrap the generated file

The generated file is named espree.cjs and it is a commonjs module. We can rename it to espree.js and wrap it as a requirejs module which means it has to be wrapped with the following code:

define(function (require, exports, module) {
     // espree code here
});

Copy the bundle

Now you can copy the bundle to this r.js fork repo.

cp dist/espree.js /path/to/r.js/build/jslib/espree.js