Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you've got time to migrate from Chirpy to Grunt, you surely have time to try a couple of different minifiers and check for one which <em>doesn't</em> break your <code>forms.js</code> module.</p> <p>What you're doing is just fine, but I would argue in favor of using just uglify for everything. In my case, I copy all the scripts to a build folder, and then just run uglify on them.</p> <p>I configured uglify like this.</p> <pre><code>uglify: { js: { files: { 'bin/public/js/all.js': 'bin/public/js/**/*.js' }, options: { preserveComments: false } } } </code></pre> <p>You can <a href="https://github.com/bevacqua/unbox" rel="noreferrer">check out the repo on GitHub</a>, it might give you a couple of ideas.</p> <p>You can determine the ordering simply by being explicit about it when you define the files in your <code>uglify</code> target.</p> <pre><code>uglify: { js: { files: { 'bin/public/js/all.js': [ 'bin/public/js/IMPORTANT/**/*.js', 'bin/public/js/something.js', 'bin/public/js/else.js', 'bin/public/js/unimportant/*.js', // you can even exclude stuff 'bin/public/js/do-not-minify/**/*.js' ] } } } </code></pre> <p>You can check <a href="http://gruntjs.com/configuring-tasks#globbing-patterns" rel="noreferrer">Grunt file globbing patterns</a> for more info.</p> <h1>Update</h1> <p>The order in which your files are described in the globbing pattern is the order in which they'll be processed, this is true for almost all tasks that take a glob in Grunt. If you can't uglify everything, I'm guessing you'll still want to concatenate. In that case, I'd advise you have a flow like the following pseudo-code, to get you going:</p> <pre><code>uglify: { js: { files: { 'bin/public/js/all.js': [ // using whichever order of importance you need 'src/public/js/**/*.js', '!the-ones-you-dont-minify' ] } }, concat: { // using whichever order of importance you need 'src/the-ones-you-dont-minify/**/*.js', '!the-ones-you-minified' } grunt.registerTask('build', ['clean', 'uglify:js', 'concat']); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POMinify some files, combine all, with Grunt.JS
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USbevacqua
    1. USbevacqua
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMinify some files, combine all, with Grunt.JS
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COcomment on your first paragraph: The issue is not with my time, it's with the full level of regression testing that would take place if I impact the forms.js (it's a VERY touchy subject around here ... forms.js is a brittle, bloated code base for some critical functionality. Refactoring that is very high on my personal priority list) ...
      singulars
      1. PO
      1. USScott Silvi
    2. CO.. and back to the problem at hand. What you just described will uglify ALL of my files, won't it? I need to minify some of them, not all. And to my edit, an add'l problem is that the load order of the files is important - some minified, some not ... so do I have to cludge up my grunt tasks to minify the ones I need to minify to temp files, then concat them in the proper order (both minified & unminifed), then grunt clean?
      singulars
      1. PO
      1. USScott Silvi
    3. COsee my updated answer
      singulars
      1. PO
      1. USbevacqua
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload