CODEWITHSUNDEEP
javascriptgruntjsyeoman
matthewbeta
matthewbeta

Reputation: 736

What is the purpose of the .tmp directory the Yeoman Gruntfile uses

A common pattern in Gruntfiles when preprocessing CSS and JS is to compile the output to a .tmp directory , process it (say with Autoprefixer or Uglify) and then copy it into the destination directory. Particularly when serving locally (eg with grunt-contrib-connect)

eg: app/sass > compile to .tmp/css > autoprefix and minify > move to dist/css

Why would this be a benefit to processing in one place and moving to the destination directory immediately? eg: app/sass > compile to app/css > autoprefix and minify > move to dist/

or am I misunderstanding the whole thing? :S

Upvotes: 2

Views: 1046

Answers (1)

Jscti
Jscti

Reputation: 14440

It's a temporary/working folder that contains files that are not yet 100% generated... It's just a pattern in order to not mix build's workflow files with build final files.

This .tmp folder is generally used by grunt plugins in the background without you noticing it.

Upvotes: 3

Related Questions