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

ts-package-scope-plugin

v1.1.0

Published

TypeScript Language Service Plugin for creating package scope.

Downloads

5

Readme

npm version Build Status Build Status

ts-package-scope-plugin

TypeScript Language Service Plugin for creating package scopes using dir names and JS Docs.

It provides IntelliSense for VS Code and error reporting using TypeScript TSServer.

Installation and usage

Install package:

yarn add -D ts-package-scope-plugin or npm i --save-dev ts-package-scope-plugin

Update tsconfig.json:

{
  "compilerOptions": {
    "plugins": [
      {
        "name": "ts-package-scope-plugin"
      }
    ]
  }
}

VS Code users

Run command TypeScript: Select TypeScript version and choose Use workspace version:

Configuration

By default, plugin will analyse the same files as the TypeScript compiler in your project. You can override this behavior by using include property:

{
  "compilerOptions": {
    "plugins": [
      {
        "name": "ts-package-scope-plugin",
        "options": {
          "include": ["./src/**/*"]
        }
      }
    ]
  }
}

Package scope

There are two ways to make module package scoped. Using suffix/prefix in folder name or setting plugin option with specific folder names.

1. package prefix/suffix

To make file package scoped using prefix/suffix it needs to be placed in folder with package in its name separated with dot ex. package.<name> or <name>.package:

project
│   README.md
│   file001.txt
│
└───package.interface
│   │   api.ts
│
└───package.domain
    │   client.ts

2. packageNames option

To make file package scoped using specific folder names, they have to be listed as an array in tsconfig.json plugin option:

{
  "compilerOptions": {
    "plugins": [
      {
        "name": "ts-package-scope-plugin",
        "options": {
          "packageNames": ["core", "domain"]
        }
      }
    ]
  }
}

When you import file from one package into another, IDE will show a TypeScript error.

Public scope

To make file available from other packages set its scope to public using JS Doc tag at the top of the file:

/** @package-scope public **/
import { Helper } from "./helpers";

export function getClient() {}

IntelliSense filtering (only for VS Code)

By default, files which are not available for current package will be removed from intellisense suggestions. To turn on or off this feature you can use intelliSense option in tsconfig.json:

{
  "compilerOptions": {
    "plugins": [
      {
        "name": "ts-package-scope-plugin",
        "options": {
          "intelliSense": false
        }
      }
    ]
  }
}