Skip to content
displays the import size of the package you are importing inside the code editor
JavaScript TypeScript
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
packages coc-import-cost: version 1.0.1 May 6, 2019
.gitignore migrate to yoshi May 21, 2018
.travis.yml Update .travis.yml Sep 23, 2017
LICENSE Create LICENSE Aug 7, 2017 Implement a coc.nvim extension (#127) May 6, 2019
appveyor.yml update node version to v8.9.1 Dec 24, 2017
lerna.json update lerna version on lerna.json to 2.5.1 Dec 24, 2017
package.json migrate from yoshi to haste Dec 24, 2017

Import Cost Build Status Build status

This extension will display inline in the editor the size of the imported package. The extension utilizes webpack with babili-webpack-plugin in order to detect the imported size. Example Image

This project includes implementation of:


Third-Party Editor Plugin Links

Why & How

I detail the Why and How in this blog post:

Developer guidelines

In this project we use lerna for managing the multiple packages.

Getting started

In order to start working all you need to do is:

$ git clone
$ npm install
$ code packages/import-cost
$ code packages/vscode-import-cost

Once VSCode workspaces are open:

  • Hit F5 to run tests in import-cost
  • Hit F5 to run the vscode-import-cost extension in debug mode

Applying changes

Thanks to lerna, we have a symbolic link in the vscode-import-cost node modules folder to the local import-cost, which makes applying changes very easy. You can verify that link exists by running the following command:

$ ls -la packages/vscode-import-cost/node_modules | grep import-cost
lrwxr-xr-x    1 shahart  staff    17 Aug  6 09:38 import-cost -> ../../import-cost

If anything goes wrong and link does not exist, just run the following commands at the root of this project and lerna will sort it out:

$ git clean -xdf
$ npm install

After you make any changes to the import-cost node module, don't forget to trigger transpilation in order to see those changes when running the vscode-import-cost extension:

$ npm test

Publishing changes

When you are ready to publish a new version of the extension, you first need to publish a new version of import-cost (unless nothing changed there). This is done by first commiting all your changes, then simply run the following commands:

$ cd packages/import-cost
$ npm version patch | minor | major
$ git commit -a -m "releasing version X.X.X"
$ git push
$ npm publish

Then go ahead and release the extension with almost same steps (except for last one):

$ cd packages/vscode-import-cost
$ npm version patch | minor | major
$ git commit -a -m "releasing version X.X.X"
$ git push
$ git clean -xdf && npm install && vsce publish

See how in the last step we had to clean everything and do a clean npm install in the extension folder? This is an important step so that vsce publish will bundle everything correctly when publishing the extension. After that's done, you'll need to run following command so that lerna will sort everything out again:

$ cd ../..
$ git clean -xdf
$ npm install

Don't forget to update with details of what is new in the released version...

You can’t perform that action at this time.