I'm getting this error when I open the stats.html in Chrome's latest version for macOS: ReferenceError: nodesData is not defined.

I'll e-mail you my file. Thank you very much.

Hi, thank you for bringing this me. I dropped pupa because it is not good to publish minor versions with breaking changes

Ok

If I ask the visualizer to open the browser by default, Avast will detect it as a virus.

I do not see from screenshot that issue is in my plugin

I've had a problem recently where a deployed lambda would fail to run if I enable the import of the sharp-phash in my code. When I removed it, it was working again. I'm suspecting that the installed sharp versions were conflicting. (I couldn't test this yet). More details of this here: https://github.com/lovell/sharp/issues/2387

The weird thing is that it wasn't causing any issues on my local mac. Only when it was deployed to a lambda where it's not so easy to debug.

This is not necessary what you think. Try to make simple image transformation and deploy to lambda. It is very possible something missing in lambda env when it is building/running sharp. If you make very simple script like, read image, resize and output e.g in different format you should see if it is this.

I think adding sharp as a peer dependency would raise other issues, like backwards compatibility and which sharp version you want to actually add as peer dep.

Well, backward compatability is not a big problem, i just increment last version i have tested. If sharp will update api i will do update and increment major version, it is how semver works. About which sharp version to install - short version is latest always (long version it see warning when you do installation about missing peer dependency and copy version range in npm i command).

So i moved sharp to peerDependencies, just install sharp-phash and last sharp.

Bumps bl from 4.0.2 to 4.0.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rvagg/bl/releases">bl's releases</a>.</em></p> <blockquote> <h2>v4.0.3</h2> <p>Fix unintialized memory access</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rvagg/bl/commit/f659836cc84211cad41b73bad89c78f7f874c626"><code>f659836</code></a> Bumped v4.0.3</li> <li><a href="https://github.com/rvagg/bl/commit/7a4ae7f818a4ceba234f3d186a1ffb3f0a34ad0c"><code>7a4ae7f</code></a> Node v14</li> <li><a href="https://github.com/rvagg/bl/commit/d3e240e3b8ba4048d3c76ef5fb9dd1f8872d3190"><code>d3e240e</code></a> Fix unintialized memory access</li> <li><a href="https://github.com/rvagg/bl/commit/1c590ad49e10a158783ada7cc0662d9e0cc6cc11"><code>1c590ad</code></a> add license MIT tag to package.json (<a href="https://github-redirect.dependabot.com/rvagg/bl/issues/83">#83</a>)</li> <li>See full diff in <a href="https://github.com/rvagg/bl/compare/v4.0.2...v4.0.3">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps lodash from 4.17.11 to 4.17.20. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/ded9bc66583ed0b4e3b7dc906206d40757b4a90a"><code>ded9bc6</code></a> Bump to v4.17.20.</li> <li><a href="https://github.com/lodash/lodash/commit/63150ef7645ac07961b63a86490f419f356429aa"><code>63150ef</code></a> Documentation fixes.</li> <li><a href="https://github.com/lodash/lodash/commit/00f0f62a979d2f5fa0287c06eae70cf9a62d8794"><code>00f0f62</code></a> test.js: Remove trailing comma.</li> <li><a href="https://github.com/lodash/lodash/commit/846e434c7a5b5692c55ebf5715ed677b70a32389"><code>846e434</code></a> Temporarily use a custom fork of <code>lodash-cli</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/5d046f39cbd27f573914768e3b36eeefcc4f1229"><code>5d046f3</code></a> Re-enable Travis tests on <code>4.17</code> branch.</li> <li><a href="https://github.com/lodash/lodash/commit/aa816b36d402a1ad9385142ce7188f17dae514fd"><code>aa816b3</code></a> Remove <code>/npm-package</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.11...4.17.20">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~bnjmnt4n">bnjmnt4n</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Hi, thanks for pull request.

You can check first if the issue really in different versions with npm ls sharp ideally it should be one.

I can merge your PR, but i think it is better to move sharp as peer dependency.

Hi. I found this great library via npm. But it was hard to find the github repo, because npm did not link it. This change adds the repository information to the package.json. On the next release, npm will add this link on the right sidebar.

Hi, thanks for PR, i will merge it after vacation

Hey @btd, thanks very much for your tool :wink: :clap:

I just tried the new gzip/brotli feature.

• When I enable sourcemap, the gzip/brotli sizes are empty.
• When I disable sourcemap, I get sizes but they seems to be based on the source before minification etc...

My build is here: https://github.com/CleverCloud/clever-components/blob/new-cdn-build/rollup-cdn.config.js and it uses this config: https://github.com/CleverCloud/clever-components/blob/d60ce9e9047329a133c2560499aac061f465c21d/rollup-common.js#L140-L145

stats.html in your emails

I think this is fixed

Hi there.

I have some trouble reading dependencies with some of our big projects with the actual colors map.

I try to dig in the treemap/color.js script but I was a bit confused on how to override colors.

May I have some clue on this ? Also the yellow part should not be as big as the pink part ? Thanks

I think this is ok for now. If you want you can play with saturation and light of colors, if you find better constants.

I tried to make a change to use less right colors. You can see in master branch i removed using d3 color scale and used plain hsl. It looks like this:

If you want you can play around with coefficients if you will find better.

Hi,

there is no way for now to override colors. I think plugin should work in most cases just as is. More options - more problems for future to support/maintain. I can agree that color palette is a bit bright ( i would add some sort of pastel colors ) if you want to do something in this area i am welcome to support/review PR. Currently rainbow coloring works such way: https://github.com/btd/rollup-plugin-visualizer/blob/master/src/treemap/color.js#L35

1. It selects number of children (it is easier number of subroot elements in one bundle or number of bundles).
2. It tries to map numbers to color pallet
3. It selects text color according background lightness

Current version uses this color scheme: https://github.com/d3/d3-scale-chromatic#interpolateSpectral Basic way to fix as it looks to me need to select something less bright.

Pink part is 2.8mb and yellow only 80kb - so no they should not be the same.

I don't how you use it if you use it, but each time you use a construct like <% _.each(... you got this message.

I had to add the import llke this:

  ...
  const intro = hasEscape ? "import escape from " + JSON.stringify(escapeModule) + ";" : "";
  const intro2 = "import _ from  'lodash';" ;

  return `
  ${intro}
  ${intro2}
  export default ${source}
  `;

I there a better way?

If i am not mistaken you can add templateOptions to plugin:

jst({ 
  templateOptions: {
    variable: 'data',
    imports: { _ }
  }
});