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

decaffeinate-coffeescript2

v2.2.1-patch.6

Published

decaffeinate fork of the CoffeeScript implementation

Downloads

64,095

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

eventualbuddhaeventualbuddhaalangpiercealangpiercedecaffeinate-botdecaffeinate-bot

Keywords

javascriptlanguagecoffeescriptcompiler

Readme

decaffeinate fork of CoffeeScript

This is is a fork of the CoffeeScript implementation with some small patches that are useful to the decaffeinate project. It also contains TypeScript types for working with the CoffeeScript AST.

It is available on npm under the name decaffeinate-coffeescript, but the intention is that it will only be useful for decaffeinate and its dependencies.

Process

The main purpose of this process approach is to make it easy to make patches to CoffeeScript while also not interfering with branch names or version numbers. Any of these steps could probably be automated, but since this fork will likely have very few changes, we'll just follow the process manually for now.

Branch/release strategy

All work is done on a branch directly off of the most recent release, currently 1.12.7. Work is done on a branch called decaffeinate-fork-1.12.7, which is also specified as the GitHub default branch. Ideally, the git history should be clean, and make it clear which changes have been made on top of the official release.

Release names are based on the CoffeeScript release, with a patch number as a suffix. So the first patch is version 1.12.7-patch.1, then 1-12.7-patch.2, etc. Semantic versioning isn't too important here since this package is just for internal use within the decaffeinate project.

Submitting a new patch

Patches are submitted as pull requests to the most recent fork branch. If the patch is a bug fix, we also make a reasonable effort to submit a PR to the official CoffeeScript repo on the master branch.

Once the patch is landed, we make another commit updating package.json with the new version number and publish the result to npm.

Dealing with CoffeeScript updates

Whenever CoffeeScript releases a new version, we will switch to a new branch based on the new release and re-apply the relevant patches using cherry-picks. We'll skip irrelevant changes like the package.json commits. This should hopefully keep the git history understandable and keep this repository focused as a small set of well-understood patches.