couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Keen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-2489) Remove libs from main require.js bundle
Date Tue, 09 Dec 2014 23:59:13 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240335#comment-14240335
] 

Ben Keen commented on COUCHDB-2489:
-----------------------------------

This was a little fiddlier than expected, but I'm almost there. The actual markup will be
slightly different, and I need to introduce an intermediary requireJS file to house the references
to the libs, for use during the requireJS optimization step. 

I'll write up a long boring explanation of how it works after it's all up and running in dev
+ prod envs.

> Remove libs from main require.js bundle 
> ----------------------------------------
>
>                 Key: COUCHDB-2489
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2489
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Ben Keen
>            Assignee: Ben Keen
>
> Right now the prod bundling process sticks everything - libs + code - into a single require.js
file. Libs seldom change, but code changes all the time. Split them so that browsers would
cache the unchanging libs file and not force an unnecessary re-download each time anything
changes. The libs to separate are: 
> - require
> - d3
> - jquery
> - backbone
> - bootstrap
> - lodash 
> - velocity, velocityUI



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message