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

forbidden-imports-tslint

v0.0.4

Published

A tslint rule to forbid imports of certain RegExes in specified paths.

Downloads

27

Readme

TSLint Rule to forbid imports in certain paths

A tslint rule to forbid imports of certain RegExes in specified paths. It is not related to but inspired by https://github.com/electroma/tslint-forbidden-imports. I did not use electroma as it does not have support for relative typescript paths1 e.g. tsconfig.json:

"paths": {
      "@shortcutToPath/*": ["./my/very/much/to/long/path/*"]
}

Usage

  • Add rule as dev dependency:
yarn add -D forbidden-imports-tslint

Assuming you have the following file structure:

  • my-client
  • client-common
    • components
    • directives
    • services
  • other-client

And the following paths are defined in your tsconfig.json:

"paths": {
      "@someOtherClient/*": ["./other-client/*"],
      "@myClient/*": ["./my-client/*"],
}

If you want to forbid each of the clients to import components from the other client and also want to forbid the common components and directives to import (unshared) components from the clients while common services have no import restriction. Define the following rule in your tslint.json:

{
  "rulesDirectory": [
    "node_modules/forbidden-imports-tslint/src"
  ],
  "rules": {
    "forbidden-imports": [true,
      {
        "my-client": ["@someOtherClient*"],
        "other-client": ["@myClient*"],
        "client-common/components": ["@someOtherClient*", "@myClient*"],
        "client-common/directives": ["@someOtherClient*", "@myClient*"]
    
      }
    ]
  }
}
  • Run tslint. In Angular you can use ng lint.

Development

To adapt this custom TSLint rule

  • install Typescript globally yarn global add typescript
  • adapt the forbiddenImportsRule.ts
  • compile it to JS -> yarn build