profile
viewpoint
Denis Bardadym btd Deutschland, München

btd/docco 15

Most advanced fork of original docco - documentaion generator

btd/connect-session 5

Connect.js session managment for Rest Api applications

btd/awslogs-stream 1

Writable stream to push logs to AWS CloudWatch Logs

btd/browserpipe 1

Small node.js application as analog for pocket and pinterest

btd/ansible-redis 0

Highly-configurable Ansible role to install Redis and Redis Sentinel from source

btd/api-blueprint 0

API Blueprint

btd/atom-ensime 0

Just a playground, do not try to use

btd/awesome-nodejs 0

A curated list of delightful Node.js packages and resources.

issue closedbtd/rollup-plugin-visualizer

ReferenceError: nodesData is not defined

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.

closed time in 3 days

mauroporras

issue commentbtd/rollup-plugin-visualizer

ReferenceError: nodesData is not defined

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

mauroporras

comment created time in 3 days

push eventbtd/rollup-plugin-visualizer

Denis Bardadym

commit sha aededd546b7e9ada9a547921e15528ba7d8891a1

Remove pupa and build template manually again

view details

Denis Bardadym

commit sha 304f370a0c1f1fdc45e8320ad7e014163a1b2ca0

v4.1.2

view details

push time in 3 days

issue commentbtd/rollup-plugin-visualizer

Avast detects visualizer as virus

Ok

aminya

comment created time in 7 days

issue closedbtd/rollup-plugin-visualizer

Avast detects visualizer as virus

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

closed time in 7 days

aminya

issue commentbtd/rollup-plugin-visualizer

Avast detects visualizer as virus

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

aminya

comment created time in 7 days

PR closed btd/sharp-phash

update sharp dependency

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

+17 -66

3 comments

2 changed files

soosgyul

pr closed time in 23 days

pull request commentbtd/sharp-phash

update sharp dependency

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.

soosgyul

comment created time in 23 days

push eventbtd/sharp-phash

Denis Bardadym

commit sha 60a8887250fe9daf7e249e33db26a94be37c9581

Move sharp to peer dependency

view details

Denis Bardadym

commit sha c14477cbcfdf25a4c38973d61591800a1e54349c

Remove option to pass sharp instance

view details

Denis Bardadym

commit sha 1db44aecd5aaf776b9a47037a844910014cbc377

Update readme to reflect changes

view details

Denis Bardadym

commit sha bec093fef89b04686a26878c408dfd4010ebcac1

Add changelog

view details

Denis Bardadym

commit sha 6c1f039b6ae925fa9130da302e8c072cb60bdd5e

v2.0.0

view details

push time in 23 days

PR closed btd/sharp-phash

Bump bl from 4.0.2 to 4.0.3 dependencies

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 compatibility score

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>

+4 -9

0 comment

1 changed file

dependabot[bot]

pr closed time in 23 days

PR closed btd/sharp-phash

Bump lodash from 4.17.11 to 4.17.20 dependencies

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 compatibility score

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>

+4 -9

0 comment

1 changed file

dependabot[bot]

pr closed time in 23 days

push eventbtd/sharp-phash

Denis Bardadym

commit sha 03a12f8cd1e33aa8c0fa5b2714a520eab0230758

Create FUNDING.yml

view details

push time in 23 days

pull request commentbtd/sharp-phash

update sharp dependency

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.

soosgyul

comment created time in 23 days

delete branch btd/rollup-plugin-visualizer

delete branch : update-yargs

delete time in 25 days

push eventbtd/rollup-plugin-visualizer

Denis Bardadym

commit sha b3ee79713a9d817405ad142f6b17f92bf9dac338

Check yargs (#81) Co-authored-by: Denis Bardadym <denis.bardadym@check24.de>

view details

push time in 25 days

PR opened btd/rollup-plugin-visualizer

Check yargs
+31 -45

0 comment

2 changed files

pr created time in 25 days

create barnchbtd/rollup-plugin-visualizer

branch : update-yargs

created branch time in 25 days

push eventbtd/rollup-plugin-visualizer

Denis Bardadym

commit sha 9127e51766872cc5cbe2217e802b9c200f75e39a

Update rest of deps (#80) Co-authored-by: Denis Bardadym <denis.bardadym@check24.de>

view details

push time in 25 days

PR opened btd/rollup-plugin-visualizer

Update rest of deps
+176 -130

0 comment

1 changed file

pr created time in 25 days

create barnchbtd/rollup-plugin-visualizer

branch : update-3

created branch time in 25 days

delete branch btd/rollup-plugin-visualizer

delete branch : update-2

delete time in 25 days

push eventbtd/rollup-plugin-visualizer

Denis Bardadym

commit sha 4bcb9de537ecd3f71f480fc2bcc721b35e898d68

Update build frontend deps (#79) Co-authored-by: Denis Bardadym <denis.bardadym@check24.de>

view details

push time in 25 days

create barnchbtd/rollup-plugin-visualizer

branch : update-2

created branch time in 25 days

delete branch btd/rollup-plugin-visualizer

delete branch : update-1

delete time in 25 days

push eventbtd/rollup-plugin-visualizer

Denis Bardadym

commit sha 4569834a2508b3fb59107ac62fcfa35f5c9cc225

Update build deps (#78) Co-authored-by: Denis Bardadym <denis.bardadym@check24.de>

view details

push time in 25 days

PR opened btd/rollup-plugin-visualizer

Update build deps
+20 -20

0 comment

2 changed files

pr created time in 25 days

create barnchbtd/rollup-plugin-visualizer

branch : update-1

created branch time in 25 days

push eventbtd/sharp-phash

Daniel Meyer

commit sha 512dae14a49c1254a7040059a4e0b7bc2c2e1c9a

ADD repository info to package.json

view details

Denis Bardadym

commit sha 6cec2721fb7499c863dec8169ce0ee3bf25a66fb

Merge pull request #7 from pubkey/patch-1 ADD repository info to package.json

view details

push time in a month

PR merged btd/sharp-phash

ADD repository info to package.json

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.

+4 -0

1 comment

1 changed file

pubkey

pr closed time in a month

pull request commentbtd/sharp-phash

ADD repository info to package.json

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

pubkey

comment created time in a month

startedreact-spring/jotai

started time in 2 months

push eventbtd/rollup-plugin-visualizer

Denis Bardadym

commit sha a38520cd79378cc70b5bdd971f9fc7f3094d8ece

Update deps

view details

Denis Bardadym

commit sha 8d589884ae6e2d9f1dc02b00b5ebd81145f992e9

v4.1.1

view details

push time in 2 months

startedtransitive-bullshit/lqip-modern

started time in 2 months

startedbtd/rollup-plugin-visualizer

started time in 2 months

issue closedbtd/rollup-plugin-visualizer

gzip/brotli size with sourcemap

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

closed time in 3 months

hsablonniere

issue commentbtd/rollup-plugin-visualizer

gzip/brotli size with sourcemap

I think this is fixed

hsablonniere

comment created time in 3 months

issue closedbtd/rollup-plugin-visualizer

Treemap - Custom colors map

Hi there.

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

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

closed time in 3 months

raphael22

issue commentbtd/rollup-plugin-visualizer

Treemap - Custom colors map

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

raphael22

comment created time in 3 months

push eventbtd/rollup-plugin-visualizer

Denis Bardadym

commit sha 1c782f9565c818695b8d1c3cca23dc35b5a28411

Drop not used var

view details

Denis Bardadym

commit sha 39c62647992b2710e386505f0486e8926d4994d2

v4.1.0

view details

Denis Bardadym

commit sha 9bd7aa887c0628d9de7cf1fe0ce7f17c21539d7e

Update changelog

view details

push time in 3 months

issue commentbtd/rollup-plugin-visualizer

Treemap - Custom colors map

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:

image

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

raphael22

comment created time in 3 months

push eventbtd/rollup-plugin-visualizer

Denis Bardadym

commit sha ee2b0f74131df06078e9abd1f2032985e44eb741

Drop filters for now

view details

Denis Bardadym

commit sha 14ecb666a178131e37d4bc8eaf650dcbad630fdf

Update deps

view details

Denis Bardadym

commit sha d904922d09c807eb600e0ca59018275af99ef80c

Change color scheme for treemap

view details

Denis Bardadym

commit sha cbcf74f30ff38a393b32ef23c92f19b14a54c854

Update changelog

view details

push time in 3 months

issue commentbtd/rollup-plugin-visualizer

Treemap - Custom colors map

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.

raphael22

comment created time in 3 months

startedvitejs/vite

started time in 3 months

issue closedbtd/rollup-plugin-jst

Uncaught ReferenceError: _ is not defined

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?

closed time in 3 months

boussou

issue commentbtd/rollup-plugin-jst

Uncaught ReferenceError: _ is not defined

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

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

comment created time in 3 months

more