Enable tree shaking

[fergiemcdowall]

I am trying to tree shake stopword

At the moment, when using a bundler such as Webpack or Rollup stopword will always include all lists of stopwords whether they are used or not. This means that bundled applications that include stopword will often be much larger than necessary.

Example
In this gist, the compiled output of npm test includes all languages even though it should only include English stopwords.

The Fix
Updating package.json as follows ->

{
// ...
  "main": "./src/stopword.js",
  "module": "./src/stopword.js",
  "browser": "./src/stopword.js",
// ...
}

However- we have to make sure that the jsdeliver version continues to be generated

[fergiemcdowall]

If I understand correctly, we only have to keep the /dist folder as-is and publish to npm in order for it to appear on jsdelivr?

[fergiemcdowall]

On second thoughts, we only need to change one line in package.json:

  "browser": "./src/stopword.js"

That said, given that the whole module is now written in ES6, there is probably no good reason not to also set this for main and module

[fergiemcdowall]

published a release candidate for testing purposes -> [email protected]

[eklem]

I'm not sure, but it may be that part of the change made Jsdelivr use go to almost zero.

Jsdelivr statistics was going down quite a lot, but not in that order of magnitude. Anyway, it could be coincidental. The most used file in v2.0.8 looks identical in v3.0.0-rc1.

https://cdn.jsdelivr.net/npm/[email protected]/dist/stopword.umd.min.js
https://cdn.jsdelivr.net/npm/[email protected]/dist/stopword.umd.min.js

[fergiemcdowall]

Hmm- strange. Publishing to npm with the tag next should have no effect on jsdelivr, but maybe I am wrong?

I can see that the value of https://cdn.jsdelivr.net/npm/[email protected] is incorrect. It should probably be the same as https://cdn.jsdelivr.net/npm/[email protected] (pointing to the umd file in /dist).

I will upload a 3.0.0-rc2 version where package.json includes the line "jsdelivr": "./dist/stopword.umd.js", as per the docs. Hopefully that will fix https://cdn.jsdelivr.net/npm/[email protected] which will then make downloads work again.

Its worth a try at least! 😅

[fergiemcdowall]

https://cdn.jsdelivr.net/npm/[email protected] looks better, so maybe downloads will pick up again..?😅

[eklem]

Nice! Hopefully it will =)

[eklem]

I'm guessing that either the change had nothing to do with the decline in use of JsDelivr as CDN, or that it was one user that has switched to another way of using the library. Or if it wasn't important for them, they have found another solution.

[fergiemcdowall]

Its very strange that the downloads should change so much, but yes, we may just have lost one "megauser"

[eklem]

I think you can release it as a proper v3.0 now.

[fergiemcdowall]

OK 👍

[fergiemcdowall]

Just published on npm (will propagate out to jsdelivr)

[eklem]

Is this issue because of the change?
#318

[fergiemcdowall]

Possibly- will take a look.