Build with vitejs

[peterpeterparker]

Changes

• drop webpack for vite
  • remove webpack dependencies
  • add various vite dependencies
  • add configuration vite.config.ts
  • convert webpack plugins - e.g. for canister IDs or to remove script or prerendering - to vite.plugin.ts
  • move and adapt html file for index.html
  • move showcase html and ts file to separate directory
• set buffer, process and stream-browserify as dependencies instead of dev dependencies because these are such
• polyfill buffer manually in index.ts
• set script to be loaded as module by canister

Remaining non-production blocker tasks in #1458.

[nmattia]

there seems to be an issue here, images are gone

[peterpeterparker]

thanks having a look

[nmattia]

is this for vite? why did all the showcase files have to move btw?

[peterpeterparker]

is this for vite?

this what?

why did all the showcase files have to move btw?

vite needs one single entry, an index.html. did not really found how to have index.html and showcase.html and having it separate is cleaner anyway.

[nmattia]

do you know why all list items changed from * to -?

[peterpeterparker]

prettier format

[frederikrothenberger]

Maybe this is a stupid question, but doesn't vite imply rollup? And isn't rollup causing all the reproducibility issues that the NNS dapp is having?
Won't this be an issue for II too?

[peterpeterparker]

Maybe this is a stupid question, but doesn't vite imply rollup? And isn't rollup causing all the reproducibility issues that the NNS dapp is having?

That's a good point, we have to test. In NNS-dapp the recent reproducibility issues had to do with packaging CSS, which has been solved in Rollup and is probably not a problem for II because the CSS is not chunked, and some recursive import on library packaged within the ledgerhq hardware wallet which we do not have neither here.

But yeah few tests is a good idea.

[peterpeterparker]

First reproducibility issue did not work so I'm trying now the option discussed in rollup/plugins#1425 (comment)

[peterpeterparker]

Reproducibility issue solved and tested @frederikrothenberger.

There was one issue discovered by @nmattia (💪). Rollup does not generate process.env code the same way if the value is defined or undefined. That lead to inconsistency at comparing the sha in the CI. Providing default value solves it - i.e. having process.env.... used in code always defined solves it.

[peterpeterparker]

Let's have a clean start. I created a patch from this PR and started a new clean one 👉 #1461