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

tslint-forbidden-imports

v1.0.9

Published

TSLint plugin to limit certain types of imports (configured using GLOB patterns)

Downloads

218

Readme

npm version Build Status Coverage Status

tslint-forbidden-imports

This rule is useful in larger code bases to control dependencies between project modules. Rule allows to specify source file patterns and list of path patterns which should not be allowed.

Example use case

For example project code has the directory layout like:

src/
    client/
    server/
    common/

Directories client, server and common represent code scopes:

  • client - application UI
  • server - server-side logic
  • common - shared constants and interfaces

In this setup imports between following directories should not be allowed:

  • client -> server (something like import server from '../../server/myAPIServer')
  • server -> client (something like import Crux from '../../client/components/Crux')
  • common -> client
  • common -> server

It may be implemented by adding the following rule configuration:

{
  "forbidden-imports": [true, {
          "client/**": ["server/**"],
          "server/**": ["client/**"],
          "common/**": ["client/**", "server/**"]
  }]
}

Installation

yarn install -d tslint-forbidden-imports

Configuration

  1. Add node_modules/tslint-forbidden-imports/rules to rulesDirectory parameter of your tslint.json.
  2. Enable rule forbidden-imports and pass mapping "file pattern" -> ["fordidden import patterns"...]

The pattern syntax may use any features supported by micromatch.

Supported import pattern types:

  • Node package (i.e. lodash or ui-*)
  • GLOB file path relative to project root (i.e. src/client/** or plugins/*/src/ui/**)

Advanced configuration: placeholders

Library has support for placeholder replacement. This rule will not allow imports between child directories of plugins directory

{
    'plugins/*/src/**': ['plugins/!(%0%)/**']
}

Development

To run tests, just run yarn test.

Project tests are based on test helper from tslint-microsoft-contrib.

References