A few concerns about the practises used in the repo.

[Ashvith10]

1. Multiple versioned JS in public:

In the public folder, for every version bump, a new JS file is added, increasing the overall size of the package. At the time-being, the size is relatively small, at ~1MB, but sooner or later, this would increase exponentially.

This could be dealt with CDN providers like jsdelivr, unpkg, cdnjs, etc, right?

2. Use of let instead of const:

In a few places, to save a few characters worth of spaces that would be introduced by const by favoring let, wouldn't it be harmful if by accident, a variable that was not supposed to be over-ridden was accidentally done?

[Tao-VanJS]

In the public folder, for every version bump, a new JS file is added, increasing the overall size of the package. At the time-being, the size is relatively small, at ~1MB, but sooner or later, this would increase exponentially.

This could be dealt with CDN providers like jsdelivr, unpkg, cdnjs, etc, right?

public directory is not part of the npm.

In a few places, to save a few characters worth of spaces that would be introduced by const by favoring let, wouldn't it be harmful if by accident, a variable that was not supposed to be over-ridden was accidentally done?

const might help catch a small set of coding bugs, but in VanJS 500+ browser-based test cases are what give us the most of the confidence on reliability.