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

@microsoft/webpack-project-references-alias

v1.2.0

Published

[TypeScript](https://www.typescriptlang.org/) introduced a feature called [Project References](https://www.typescriptlang.org/docs/handbook/project-references.html) in version 3.0.

Downloads

246

Readme

Webpack alias generator for TypeScript project references

Description

TypeScript introduced a feature called Project References in version 3.0.

Project References required compiled .d.ts files either checked-in or generated after each branch switch. Not doing this would result in a broken IntelliSense experience.

This drawback was fixed in version 3.7. The TypeScript language server can now inderstand project references. This improves the IntelliSense experience across projects while removing the need to have the compiled files on disk.

The goal of this package is to provide a tool to make webpack understand project references as well. This is needed when optimizing build time when using transpile-only loaders (ts-loader in transpile-only mode or babel-loader) without the need to have the generated files on disk.

This package create aliases that makes webpack resolve the TypeScript files instead of the generated JavaScript files.

For instance, when package A is a referenced project, the alias will let you do the following import:

import "A/lib/foo"; // webpack will resolve A/src/foo.ts

Usage

const { getAliasForProject } = require("@microsoft/webpack-project-references-alias");

module.exports = {
  entry: "./src/index.ts",
  mode: "production",
  output: {
    path: path.resolve(__dirname, "dist"),
    filename: "bundle.js"
  },
  resolve: {
    extensions: [".ts"],
    alias: getAliasForProject()
  },
  module: {
    rules: [
      { test: /\.ts$/, loader: "ts-loader", options: { transpileOnly: true } }
    ]
  }
};

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.