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

@rehearsal/codefixes

v2.3.2

Published

Rehearsal Dependency Codefixes Collection

Downloads

29

Readme

@rehearsal/codefixes

Rehearsal Dependency Transforms Collection based on TSC Diagnostic

Rehearsal leverages the TypeScript Language Service for file transformation. The supported transforms are enumerated in ./src/codefixesMessages.json. This file is used to generate runtime TypeScript code that is leveraged during transformation, tests and generates documentation.

Adding New Codefixes in Rehearsal (TypeScript Language Service)

To add a new codefix to Rehearsal, which uses the TypeScript Language Service for file transformation, follow these steps:

  1. Identify the codefix you want to add from the list of codefixes in TypeScript.

  2. Open the file ./src/codefixesMessages.json in Rehearsal and add a new entry with the following information:

  • entry key: This should be the same as the codefix's fixName. You can find it from the values of the first parameter of createCodeFixAction* functions related to the codefix file.
  • title and description: These will be used in the generated Supported-Fixes.md documentation.
  • messages: These are the codes of messages related to the codefix. You can find them from the values of the third parameter of createCodeFixAction* functions in the codefix file.
  • diagnostics: These are the diagnostic codes related to the codefix. You can find them from the values of the first parameter of the registerCodeFix function in the codefix file.
  1. Create new directories in ./test/fixtures/ts-codefixes to add failing and passing fixtures for the newly added codefix.

  2. Write a test within ./test/codefixes.test.ts to test the functionality of the codefix. It's essential to add the test for the codefix; otherwise, the test suite will fail.

  3. Run pnpm generate command to regenerate the documentation and the runtime codefix objects.

  4. Finally, run pnpm test to ensure that the newly added codefix passes all the tests. This step verifies the correctness and reliability of the codefix.

By following these steps, you can successfully add a new codefix to Rehearsal and make it available for use in TypeScript Language Service transformations.