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

@cdklabs/eslint-plugin

v1.1.0

Published

eslint rules published by the CDK team. Contains CDK rules and others.

Downloads

167,206

Readme

eslint-plugin-cdk

Eslint plugin for the CDK repository. Contains rules that need to be applied specific to the CDK repository.

Rules

  • invalid-cfn-imports: Ensures that imports of Cfn<Resource> L1 resources come from the stable aws-cdk-lib package and not the alpha packages. Rule only applies to alpha modules.

  • no-core-construct: Forbid the use of Construct and IConstruct from the "@aws-cdk/core" module. Instead use Construct and IConstruct from the "constructs" module. Rule only applies to typescript files under the test/ folder.

  • no-invalid-path: Checks paths specified using path.join() for validity, including not going backwards ('..') multiple times in the path and not going backwards beyond a package's package.json.

  • no-literal-partition: Forbids the use of literal partitions (usually aws). Instead, use Aws.PARTITION to ensure that the code works for other partitions too.

  • consider-promise-all: when using Promise.all(), attest that there is no unbounded parallelism.

How to add new rules

  • Make a new file in lib/rules. It should export one function called create. The create function should return a visitor object.
  • Add the new file to lib/index.ts.
  • Add a fixture directory under test/fixtures/<rule name>. Copy and adjust an eslintrc.js file from another test.
  • Add a testing .ts file, and be sure to add either an expected.ts or an .error.txt variant as well!
  • You can now run the test in debugging mode (make sure to have npx tsc -w running, then from a debugging terminal, npx jest --no-coverage -it 'your rule name'), set a breakpoint, and inspect the typeless objects.

Use https://ts-ast-viewer.com/ to get a feel for the AST you're trying to analyze. Note that eslint uses estree to model AST nodes (not the TypeScript AST nodes), but they are often comparable. Add type-testing TypeScript helpers to type-checkers.ts for typing assistance.

To activate it for real on the repo, also add it to cdk-build-tools/config/eslintrc.js.