> To run the library locally and be able to see your changes without having to publish a new version use [npm link](https://medium.com/dailyjs/how-to-use-npm-link-7375b6219557)

Resolver plugin to help remove duplicate dependencies caused by `npm link`

Stub package for testing npm link

A `npm link` equivalent for remote, unpublished npm modules.

NPM Link: https://www.npmjs.com/package/@polyfillhq/eslint-config

[![Travis][travis-image]][travis-link] [![Downloads][downloads-image]][npm-link] [![NPM version][npm-image]][npm-link] [](https://www.npmjs.com/package/datafire) <!--[![Dependency status][deps-i

``` cd meson-components npm run build npm link

## 开发环境 ```sh npm link npm link epg-api npm unlink epg-api ```

**TLDR**: _A bit like `npm link`, but for workspaces / monorepos :rocket:_

- `sudo npm link` get link from path - `cd client` - `sudo npm i (path from npm link`

If you want to use the local version of the library in the catalog for development purposes, you can use npm link.

Automatically `npm link` all your packages together!

Like 'npm link', but doesn't trip over with symlinks and local node_modules of linking target.

npm link without installing modules

This is a CLI tool that intends to be a better yarn/npm link

Replaces npm link with something that actually works!

- link the package for local development ```sh npm link ```

TypeScript definitions for npm-link-up.

CLI utility that checks whether a project's current node modules tree contains npm-link'ed packages

Follow these steps to run the project locally using `npm link`: