[LRUG] resolving JS dependencies on deploy

[Tom Armitage]

On Thu, Nov 19, 2015 at 4:13 PM, Mark Burns <markthedeveloper at gmail.com>
wrote:

> > onerous npm-derived asset preprocessing
>
> I'm curious about this statement.
> Is it that you are loathe to have to put in the groundwork now for little
> benefit or that the asset pipeline is less onerous?
>

Well, it’s that I have a working application that’s entirely fine, and
which utilises the asset pipeline, and I am wary of the big leaky
abstraction of “adding a completely different serverside platform” into the
mix just to pull down an external dependency. I tend to think that “just
install npm” is a significant dependency, not a trivial one. But it’s
onerous because of the unnecessary change it introduces at this phase, and
because of the scale of the dependency.


> IMHO the tooling around the node ecosystem feels a lot more modern and
> suited to the task than the cludgy asset pipeline.
> Things like webpack, ES6, requirejs etc are fantastic for modern js
> development.
>

Well, yes, although again, I’ve been getting on fine! There’s only one
component of this application that resembles a single-page application; the
rest is fairly straightforward transactional web pages. I’m well aware my
front-end JS could probably be brought up to the mark in terms of
trendiness - and I like the principle of ES6, if not the transpiler. I
guess I’m being conservative in introducing new ideas to the project when
most of it works fine as it is.

Hence trying to find a solution beyond “replace your entire front-end
tooling!”
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20151119/3bd7b918/attachment-0002.html>