Component doesn't scale well for large projects

[domachine]

We're currently developing a huge application with thousands of components. But what gets me scared is that the build-size grows up like hell. 93% of the resulting build file consist of require.alias stuff. Any idea on how to reduce this?

[micky2be]

There is already an issue open on builder.js
You are welcome to complain there 😉
componentjs/builder.js#117

[jonathanong]

yeah it kind of sucks right now. some of my builds are like 50% aliases, but after gzip it's generally < 5% so i wouldn't really consider it a big deal.

in the future, aliases will be removed: componentjs/builder.js#130

going to close this since it's more of a builder issue. ill tag all the alias issues in that repo to make it clearer.

[tj]

i've got part of it done, I'll try and finish that up this weekend

[tj]

or as a quick hack for now we could completely remove the faux path stuff & resolution, since we don't have semver support right now anyway haha

[anthonyshort]

Semver. Meh. Don't think I've needed the entire past year. It's a little overrated.

[timoxley]

@anthonyshort you won't notice semver when it's working.

You also won't notice semver when components are small enough that the interface will rarely need to change. But imagine if express didn't use semver and tried to do something drastic like swap the order of arguments to res.send. many gifs would be posted.

[tj]

it's definitely a slightly different case with client stuff since you ideally have no duplicates, but that should definitely be up to the dev to resolve, I'll start working on this alias fix and a new registry this weekend

[anthonyshort]

@timoxley True, but if your app is working and you've got fixed versions everywhere, then your app won't ever break. With the fuzzy semver version you could break your app if the author is a jerk about their versioning.

[tj]

yeah at that level I think semver is pretty useless but on the client we're a bit screwed if 5 libs use emitter 0.8.0 and 2 use 1.0 or something like that

[matthewmueller]

We ran into problems with scaling component too :-(... personally I think getting the dependencies right is more important than duplicates. We could use warnings (Warning you are requiring: emitter@0.8.0, emitter@1.0.0) or like component doctor to allow for build optimizations.

[TooTallNate]

we're a bit screwed if 5 libs use emitter 0.8.0 and 2 use 1.0 or something like that

According to semver, those 2 versions should be API compatible, and thus only one copy of v0.8.0 should be included in the build.

[tj]

@TooTallNate yeah I know, that's what I'm saying, because right now that won't work. @matthewmueller agreed, im not saying we don't need it.

[timoxley]

@TooTallNate also note according to semver:

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

[tj]

</offtopic>