Personally I wouldn't create a new major version for this. 1.5 MB is not that much. But if a new major comes around anyway, I would like to see it in there, for the following reasons:

A lot of modules have a dependency on handlebars, so it gets pulled into the node_modules directory with those modules. It may even occur multiple times in the dependency-tree, which means that the 1.5 MB easily add up to three, six or even more MB.
Disk space is cheap on the server, but not all of those modules are server modules. Some are parts of build-tools or documentation-tools. That means, Handlebars may also be included in the devDepencendies of possibly all 20 or more modules in my workspace.

My more general point is: Just because disk space is cheap on the server doesn't mean we should waste it. It may not have an impact on a production machine, but it certainly has during development.

My bootprint-package needs 62 MB of hard-disk-space and if you don't have a recent computer with SSDs, you have waited quite long time to download and install everything. Waiting is not a good user-experience.
61 MB are occupied by dependencies, so I have to research where the space is wasted. Then I have to file issues and hope that the maintainers are willing to do something about it. I have had a look at the bootprint-dependencies and found out that 8.1 MB are test-files of LessCss.
I haven't looked through all dependencies yet, but Handlebars is in there as well...

Drop individual AMD files from build output #1096

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions