# Using the NPM plugin

**URL:** <https://community.weweb.io/t/using-the-npm-plugin/4752>\
**Category:** How do I?\
**Created:** [October 5, 2023, 4:36pm UTC](https://community.weweb.io/t/using-the-npm-plugin/4752 "2023-10-05T16:36:06Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![dorilama](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/dorilama/32/10403_2.png) [@dorilama](https://community.weweb.io/u/dorilama)\
**Post date:** [October 5, 2023, 7:29pm UTC](https://community.weweb.io/t/using-the-npm-plugin/4752/6 "2023-10-05T19:29:27Z")

</div>

> [@caffeinatedwes](#):
>
> This is a package that can be installed, as it is available on [unpkg.com](http://unpkg.com).

Every package published on npm is served by unpkg. It doesn’t mean that is usable as is on the browser, and if it works on the browser it doesn’t mean that it works with the plugin.

As I said [here](https://community.weweb.io/t/where-to-see-new-update-notes/4728/8) it looks like that libraries need to be packed as umd, need to add an instance to the window and need to correctly specify what file unpkg needs to serve.

---

_[View the full topic](https://community.weweb.io/t/using-the-npm-plugin/4752)._