Open FND opened 10 years ago
seems like browserify is the preferred solution these days - with the advantage of nicely explicit dependencies
I'm glad that second link acknowledges how quickly things change and how somewhat inane that is.
Indeed, yet browserify seems like a milestone with significant benefits for structuring code - though of course it also introduces significant complexity (requires a build step, no more 1:1 correspondence WRT source code).
(Also note this comment regarding JavaScript's build systems.)
we're using a fair amount of CSS and JavaScript files now, all of which are being loaded separately
this is not great for performance, so we should concatenate (and optionally minify) those assets
note that currently different pages use different assets - we should consider just having one set of assets for the entire application (or maybe two, treating edit mode separately)
(this should probably be done before #22)