Permalink
Fetching contributors…
Cannot retrieve contributors at this time
1075 lines (741 sloc) 94.1 KB

2.3.32 - March 14 2014

Minor Changes

2.3.31 - February 11 2014

Minor Changes

  • mimosa #433 removes the customFds deprecation warning on startup for node v0.12.0.

2.3.30 - January 30 2014

Minor Changes

  • skelmimosa #31. mimosa skel:new will now run a npm install inside the created project.

2.3.29 - January 27 2014

Minor Changes

  • mimosa #429. If no files in source directory, user is warned and workflows continue, previously processing would hang.
  • Mimosa core has been updated to latest chokidar.

2.3.28 - January 22 2014

Minor Changes

  • More work with mimosa-live-reload to get CSS reloading to work properly in Chrome.

2.3.27 - January 22 2014

Minor Changes

  • Adjusted how source map comments are included in transpiled JavaScript files.

2.3.26 - January 12 2014

Minor Changes

  • mimosa #422. Now calls to logger.fatal will automatically exit with non-0 status code.

2.3.25 - December 30 2014

Minor Changes

  • Using util.inspect to avoid circular logging issues.

2.3.24 - December 19 2014

Major Changes

  • mimosa-combine #19. mimosa-combine now includes, by default, source maps for the files it combines. These source maps will not incorporate existing source maps, and they will not factor in any changes made by transform functions.

Minor Changes

  • mimosa #420. Handle circular references among CSS imports.
  • mimosa-combine #21. Since they are not used, existing source maps are removed from combined files before they are combined.

2.3.23 - December 15 2014

Minor Changes

  • mimosa-jscs continues to improve, adding support for maxErrors, additionalRules, and esnext
  • mimosa-combine #14. Added an include option that allows you to pick and choose specific files to be included. This lets you pick a few to include from a large group of files in a folder rather than have to exclude a large list.
  • mimosa-combine. Addressed issue involving removeCombined and multiple folder entries.
  • mimosa-combine #15. Fixed an issue with binary files being removed unexpectedly.
  • mimosa-combine #16. Added ability to provide custom transforms that can modify files being transformed before they are combined. Details here.
  • mimosa #418, mimosa-restart. mimosa-restart has been updated to allow for configurable restart paths and to allow for mimosa to be restarted when things are both removed and updated. The example config has a really good example of how this would be used, which includes restarting mimosa when the mimosa-config is updated.

2.3.22 - December 10 2014

Major Changes

  • New Module: mimosa-ember-env will include EmberENV setup calls at the top of your ember.js vendor libs.
  • New Skeleton: MimosaEmberHTMLBars. The Cadillac of Ember + Mimosa skeletons. Includes support for HTMLBars, QUnit/Testem, automatical Ember module manifest generation, EmberENV inclusion, as well as all the other features that come with most Mimosa apps: live reload, server support, Bower integration, ES6 module transpiling, SASS compiling (via node or Ruby), a all sorts of minification/concatenation/optimization.

Minor Changes

  • Updated validations to add excludes and allow includes to behave like excludes.

2.3.21 - December 4 2014

Minor Changes

    • New Module: mimosa-jscs wraps the popular JSCS tool which performs JavaScript style checking.
  • esperanto-es6-modules. Updated to latest esperanto (options changed, so check it out before upgrading) which includes support for source maps.
  • mimosa-require #41. Shims and shim depedencies will now have their paths checked against directory aliases.

2.3.20 - November 19 2014

Minor Changes

  • Bumped mimosa-live-reload to latest socket.io to bypass some installation issues.
  • mimosa-testem-simple. Adjusted to handle when configFile is not array (as with testem-require).
  • mimosa-testem-require. Bumped to latest testem-simple.

2.3.19 - October 26 2014

Major Changes

  • mimosa-sass now includes inline (dynamic) source maps for node compiled SASS.

Minor Changes

2.3.18 - October 13 2014

Minor Changes

2.3.17 - September 24 2014

Minor Changes

2.3.16 - September 23 2014

Major Changes

  • New Module: mimosa-esperanto-es6-modules. Transpiles es6 module syntax to es5 commonjs/amd. esperanto is a faster more straight forward alternative to the es6-module-transpiler. It is for now a little less flexible, but if you do not have a mix of named and default exports in your application it is 100% worth making the switch to use esperanto.
  • mimosa-require #40. Files with nested require('') and require([],function(){}) calls should no longer be flagged as main modules.

Minor Changes

  • Updated mimosa-minify-css to latest version of clean-css, also fixed small syntax error in coffeescript doc output.

2.3.15 - September 14 2014

Minor Changes

2.3.14 - September 14 2014

Minor Changes

  • mimosa-require had a small change to when it ran its code in mimosa's workflows to allow for other modules to get their tasks done before mimosa-require runs validation.

2.3.12/2.3.13 - September 11 2014

Major Changes

  • Upgraded Module: mimosa-testem-simple has received some upgrades. It is now written in JavaScript. It now has a suite of tests for most of its functionality. The messaging as been improved slightly. And you can now pass multiple testemConfig files if you have multiple test harnesses.

Minor Changes

  • Updated validators so that when an property is set to false it isn't considered not being there.

2.3.11 - September 9 2014

Minor Changes

  • Updated validators so that isObject no longer accepts null and the validations that expect things to exist don't just check null.

Major Changes

  • New Module: mimosa-defeature will slice flagged features out of an application at build time. Effects CSS, JavaScript and templates. Use this to hide features that aren't quite ready, or to remove features from a product that a client doesn't need or hasn't paid for.
  • New Module: mimosa-minify-json will.. minify JSON! As with all minification modules, minification occurs when the -m/--minify flag is ticked.
  • Upgraded Module:mimosa-require has been updated to use the latest require.js, but Mimosa core has not been updated to use the latest mimosa-require. Read more about why.

2.3.9/2.3.10 - September 1 2014

Minor Changes

  • Updated validatemimosa so that modules have utility methods for checking RegExp and boolean
  • Addressed timing issues with mimosa-server-reload that caused the reload to fire at the end of startup.

2.3.8 - August 28 2014

Major Changes

  • New Skeleton: MimosaTypeScript. The first TypeScript skeleton! This includes the new improved typescript compiler support (see next bullet) but also includes a Hapi server, Less for CSS pre-processing, and dust for templates.
  • mimosa-typescript #1. Major upgrade in TypeScript support. Adds source maps, adds ability to exclude .d.ts files from compilation. Upgrades typescript library itself to latest.

Minor Changes

  • To support some work for the typescript compiler, added isVendor flag to file object prior to calling javascript module compile functions.

2.3.6/2.3.7 - August 23 2014

Minor Changes

Major Chnges

2.3.5 - August 21 2014

Minor Changes

  • mimosa #407. Addressing issues with an empty .mimosa_profile.

2.3.4 - August 21 2014

Minor Changes

  • Fixed small bug in validators noticed after pulling them out of mimosa.

2.3.3 - August 21 2014

Minor Changes

  • To ease testing of modules, Mimosa's configuration validation code has been pulled out and placed in a separate NPM module: validatemimosa. Mimosa now includes this library. But now Mimosa modules can include this library as a testing dependency to test and validation routines it runs through.

2.3.2 - August 20 2014

Major Changes

  • New Module: mimosa-ember-module-import will use some conventions to build out a complete set require definitions for all your Ember related code. See the GH for details.
  • New Module: mimosa-start-server will start your server at the appropriate time. No need to return a server object. Conitnue using mimosa-server if you are using the default server or need anything like live reload or server reload.
  • New Skeleton: MimosaEmberSkeleton uses the new ember-module-import is a port of the Ember Blogger example. Uses ES6 modules, automatic ember manifest generation, SASS, Express and comes ready to optimize and bundle. This skeleton is loaded and ready to go. Testing support for Ember coming soon!
  • mimosa #406. New with this release is the introduction of default profiles. Profiles are a powerful and popular feature. Using a profile is easy enough, mimosa build -P <<profile name>>, and recent releases have allowed you to chain together multiple profiles, mimosa build -P profile1#profile2#profile3. But if you have a set of profiles that you are constantly applying, you find yourself typing -P <<profile name>> quite a bit. Now you can keep a default profile in a .mimosa_profile file at the root of your project. This file, a \n-delimited list of profile names, will be the first profiles applied. You can also append -P <<profileName>> and those profiles will be applied last (and therefore override any settings in a default profile).

2.3.1 - August 13 2014

Minor Changes

  • mimosa-require #39. mimosa-require will no longer turn off a forced recompile if another module has chosen to force one.

2.3.0 - August 12 2014

Huge Changes

  • mimosa new has been updated to include a new server option: Hapi. Now with mimosa new you can get a Hapi project ready to go with one of the templating options (Jade, Handlebars, Hogan, Dust, EJS, HTML).
  • mimosa new has been updated to include a new server option: Express w/socket.io. This delivers the same Express skeleton, except with socket.io already included.

Major Changes

  • New Module: mimosa-rpm-package works much like the popular web-package module, but uses easy-rpm to create an RPM archive of an application.
  • New Skeleton: hapi-angular-browserify. An Angular app served up via Hapi and bundled with browserify. Is coded in CoffeeScript.
  • mimosa new has been updated to deliver the latest Express: 4.7.2
  • mimosa-live-reload has been updated to solve a recent issue with updating CSS in Chrome. Previously CSS would not update in Chrome until Chrome received focus. So if you were in your text editor and made a change, you'd have to hover over Chrome to see the change take effect. This is fixed. The solution is slightly hacky but the result is what you'd expect, the CSS is re-evaluated whether focus is given or not. It solves the problem by first breaking the URL of the stylesheet before fixing it. This is transparent while staring at the UI, but if looking at the network pane, you'll see a red line where the UI attempted to bring in a file that did not exist. This will just have to be documented, understood and ignored. This behavior will only take place in Chrome. All other browsers will continue to work the same way.

Minor Changes

  • All of the libraries delivered by mimosa new are updated to the latest version.
  • Addressed timing issues with mimosa-server-reload. Now server should not be restarted until the previous instance has been fully closed out.
  • mimosa-minify-js added a mangleNames property to the minifyJS config. It defaults to true, which leaves current functionality intact but when set to false variable names will not be altered.
  • mimosa-server had all its built-in template compilers updated to the latest.

2.2.21 - August 6 2014

Minor Changes

  • Removed leftover logs from sync debugging.

2.2.20 - August 1 2014

Major Changes

  • mimosa-require had a small (1-line) update that resulted in big performance improvements for large requirejs based applications. Some of the developers on my team (without SSDs) saw the speed of their build cut in half. I highly recommend you check it out. I'd love to get some time mimosa build diffs from folks upgrading to 2.2.20.

Minor Changes

  • mimosa-csslint now runs beforeWrite which allows any transforms to occur to css prior to being linted. For instance, if using the autoprefixer module, this allows for vendor prefixes to be applied before running CSSLint.
  • mimosa-just-copy #3. Previously just-copy was only capable of "just copying" files to the output location Mimosa would have otherwise copied the file. A great PR added the ability to specify an entirely different output location for input files. See the docs for details.
  • mimosa-handlebars #1, fixed the client library, making it the same version as the compiler.
  • mimosa-emblem, fixed client library bug.

2.2.19 - July 28 2014

Major Changes

  • New Module: mimosa-fix-rjs-ember. Addresses issues with r.js optimization + ember.js beta/canary builds

Minor Changes

2.2.18 - July 14 2014

Minor Changes

2.2.17 - July 13 2014

Major Changes

  • mimosa-web-package #20/mimosa-web-package #22. Huge archive generation updates. web-package can now create a .zip file for you. Additionally you can set archiveName to null to not generate an archive at all. And "mimosa-config-documented.coffee",".mimosa","bower.json" were added to the default set of files to leave out of the archive. web-package was bumped to 2.0.

Minor Changes

  • mimosa #403. The signature to retrieveConfig, used when creating commands (like mimosa sprite) from external modules, has been simplified to opts, callback. This allows for things like profiles to be passed. The previous signature, buildFirst, debug, callback is still supported. The previous first paramter, buildFirst should be attached to opts as opts.buildFirst and debug as opts.mdebug.
  • mimosa-jade #20. Updated jade-runtime to latest. Updated jade to 1.3.1.

2.2.16 - July 7 2014

Major Changes

Minor Changes

  • mimosa now assigns isVendor flag to individual files in its options.files array for processing of CSS.
  • mimosa-web-package #21. Now properly handling users possibly having coffeescript 1.6 v 1.7.

2.2.15 - June 30 2014

Minor Changes

  • mimosa #398. Updated mimosa new message to be more clear.
  • mimosa-web-package #21. Fixed mismatch between what new coffeescript projects were outputting as version numbers and what web-package was outputting for its app.js file.

2.2.14 - June 23 2014

Major Changes

mimosa #397. You can now provide multiple profiles at the command line. Ex: mimosa build -P foo#bar. Profiles are applied from left to right. So, in this case if the bar profile contains the same configuration as the foo profile, the bar profile information will overwrite foo.

Minor Changes

  • mimosa-server #6. Exposing the server file and the server object on the mimosaConfig. Can now access file and object from anywhere that has access to mimosaConfig.
  • mimosa-server-reload #7. Calling preMimosaRestart function if it exists to allow users to clean up connections, etc before restarting server.

2.2.13 - June 22 2014

Major Changes

  • New Module: mimosa-cjsx. A Coffeescript + React/JSX compiler.

Minor Changes

mimosa #396. Added --nolazy pass-through to node.

2.2.12 - June 19 2014

Major Changes

  • New Skeleton: knockout. Knockout, RequireJS, Less, Bower, Jasmine.

Minor Changes

2.2.11 - June 7 2014

Minor Changes

  • mimosa-require #35. r.js rebuilds should now happen on file change during mimosa watch.
  • mimosa-require #36. Fixed issue with module based builds bombing during mimosa watch. Should be able to re-run builds with file changes during mimosa watch.
  • mimosa-es6-module-transpiler. Upgraded to latest transpiler version, added inferName config.

2.2.10 - June 7 2014

Minor Changes

  • mimosa-live-reload #5. live-reload will now just refresh your CSS rather than reload the page if your "additional directories" have a .css file that changes.

2.2.9 - June 2 2014

Minor Changes

  • mimosa #395. Invalid bower.json will no longer crash mimosa watch after startup.

2.2.8 - May 30 2014

Minor Changes

  • Bumped version of mimosa-minify-js

2.2.7 - May 28 2014

Minor Changes

  • mimosa #392. Added watch.delay to handle cases when file events are sent before the file is finished being saved.

2.2.6 - May 19 2014

Major Changes

  • Related to mimosa #391, the misc compiler type -- added a month or so ago to represent those compilers which don't fit neatly into copying, javascript/css transpiling or template compiling -- have been thought through a bit more. Now files having an extension mapped to a misc compiler will be read, their output will be written, and their output will be cleaned up during clean processing.
  • All compilers are wrapped in a parent for their type. So, in mimosa core, there is a JavaScript compiler wrapper for all the JavaScript compilers. Previously, that wrapper would call a compile function on its wrapped compiler and that was the only compiler function that would get called as part of workflow processing. Now a compiler can register for anything else by implementing its own registration function like every other non-compiler module.
  • To see a sample misc compiler, checkout the MimosaMiscCompilerExample project.

Minor Changes

  • mimosa-server #5 (@ropez). This PR adds the ability for the mimosa-config to set variables for the views that Mimosa's default server uses from a Mimosa application. server.views.options will now be added to the global variable config for a server view before serving it, allowing you to add custom variables to your server templates.
  • mimosa #391. Add misc to compiler extension array.

2.2.5 - May 13 2014

Major Changes

  • As a part of mimosa-bower #37, a new flag has been added to the watch, build and clean commands. Add a -C/--cleanall and as Mimosa starts up it will remove the .mimosa directory. This allows for a forced reinstall of Bower components and forces other modules to rebuild their .mimosa cache.
  • New Module:mimosa-restart. Restarts Mimosa within the same process when the watch.compiledDir is deleted.

2.2.4 - May 09 2014

Major Changes

  • New Module:mimosa-svgs-to-iconfonts. Turns sets of .svg files into sets of .svg, .eot, .woff, .ttf font files and a corresponding .css file. Check out the example app to see it working.
  • mimosa-server's server and mimosa's watcher will now respond to a STOPMIMOSA signal that is sent through the Mimosa process via process.send( "STOPMIMOSA" );. This will more easily allow forked processes to shut down all of a Mimosa's process' activities.

2.2.2/2.2.3 - May 6 2014

Major Changes

  • More performance improvements, almost entirely lazy loading of libraries.

2.2.1 - May 5 2014

Major Changes

  • Beginning process of speeding up startup performance. Delayed loading of modules in skelmimosa and in mimosa core. Should improve startup a good deal. More to come.

Minor Changes

  • mimosa #390. Fixing bug introduced with 2.2.0, mimosa startup getting stuck if no javascript files have changed.

2.2.0 - May 5 2014

The slim possibility of a breaking change with mimosa #382 necessitated the bump to 2.2, otherwise the number of changes to Mimosa's core was minimal. It has been awhile since there was a release and plenty of modules and skeletons have been released since.

Wrapping up and releasing this change to core clears the way to get back to features and bug fixes with various key modules.

Next up is an attack on startup time. Mimosa is super-fast once it gets going, but it can be a bit of a bear when it first starts up and there are a number of simple changes that can be made that should begin to address that.

Major Changes

  • New Skeleton: marionette-semantic. Marionette, RequireJS, Express, Jade, Bower, CoffeeScript, LESS, Semantic-UI and more.

  • New Module:mimosa-testem-qunit. A port of the mimosa-testem-require module to use qunit instead of mocha.

  • New Module: mimosa-d3-on-window. Attaches d3 to the window object by modifying the source library. Allows for continuing to use bower to pull in d3 as build tool will always update d3 to attach it to window.

  • New Module: mimosa-adhoc-module. A super simple and super powerful module. This module lets you register simple one-off modules that are local to your codebase by simply requireing them into your mimosa-config.

  • New Module: mimosa-jade-static. A new template compiler, jade-static automatically executes compiled jade templates to generate the HTML. It then does all that normal template compilers do. It merges the HTML strings into a single file.

  • mimosa #382. Mimosa is heavily extension based. Mimosa and its modules determine when to do what based on a file's extension. Occasionally the same extension needs to have different things done. One example is when you want to have some .html based templates bundled together by Mimosa's HTML-Template compiler and you want to have some .html files simply copied from the source directory to the compiled directory. In that case two dramatically different compilers need to be invoked for the exact same file types.

    With 2.2 some things have changed with how compilers sort themselves out. Chiefly, those compilers that self-identify as copy or misc (as opposed to javascript, css or template) will be sorted to the end of the queue for priority for processing a file. copy is very much a default sort of behavior, and if anything else wants to manage a file that is also managed by the copy compiler, copy should not win that conflict. So, as in the case above, if both the template compiler and the copy compiler both want to process an .html file, the template compiler will win.

    There is minor potential for this change to cause people some trouble, but it is largely unlikely. Still, it was worth the larger version bump.

Minor Changes

  • mimosa-coffeelint #3. Via PR, coffeelint will now lint iced coffeescript files assuming you are using the mimosa-iced-coffeescript compiler.
  • server-template-compile. server-template-compile now will prettify HTML output if not using minify or optimize flags.
  • mimosa-web-package #12. npm install is now run with --production flag.
  • mimosa-web-package #13. Added .travis.yml to list of default excluded files from bundle.
  • mimosa-web-package #14. Added useEntireConfig setting. Previously web-package would pluck what it thought was the important portions of the mimosa-config out and create the config.js with it. This setting allows for using the entire config.
  • mimosa-coffeelint #4. Improvements to logging.
  • mimosa-stylus #2. stylus compiler now supports @require syntax for bringing files in.

2.1.22 - Mar 29 2014

Minor Changes

2.1.21 - Mar 26 2014

Major Changes

Minor Changes

2.1.20 - Mar 23 2014

Major Changes

  • New Module: mimosa-vault. Mimosa module which uses the vault project to generate passwords derived from a secret key.
  • New Module: mimosa-inline-css-import. Will inline your CSS @import code into your stylesheet.
  • mimosa-require #31. mimosa-require now has better support for require.js plugins. A new require.verify.plugins config allows you to configure which plugins you are using and what the extensions for those plugins are so the plugin paths can be validated.

Minor Changes

2.1.19 - Mar 17 2014

Major Changes

  • New Skeleton: react-backbone. A React, Backbone, Require.js, Bower Todo App.
  • New Module: mimosa-react. A new JavaScript compiler. This compiles your React/JSX templates to JavaScript.
  • New Module: mimosa-uncss. Run this module over your css files and eliminate all the unused CSS from your application. I ran this over my company's corporate sit and saved 77%!

Minor Changes

  • mimosa & mimosa-ractive #1. Mimosa's template compilers come with their own client libraries. The determining factor for whether or not mimosa writes those libraries has been whether or not you are using AMD. Not long ago a writeLibrary config property was added. This properly will now determine whether or not to write the client library.
  • mimosa-web-package #11. Now properly registering coffeescript/iced in app.js.

2.1.18 - Mar 10 2014

Minor Changes

  • mimosa #379. mimosa-bower now handles package.json main a bit better, checking to see if the reference is to a folder/file and adjusting accordingly.

2.1.17 - Mar 7 2014

Minor Changes

  • Added file.write helper to mimosaConfig being passed around. Saves modules from needing to deal with recursive directory creation.
  • mimosa-testem-require #10. Via PR all the libraries, sinon, chai, mocha, and sinon-chai, have been upgraded to their latest versions.
  • mimosa-ember-handlebars #3. Updated the Ember portion of the compiler.

2.1.16 - Mar 7 2014

Minor Changes

2.1.15 - Mar 5 2014

Major Changes

  • A vast majority of the mimosa-config-documented.coffee properties will now show up uncommented. This should make the -documented file easier to read and make it play nicer with syntax highlighting.

Minor Changes

  • mimosa-emblem has been updated to the latest versions of emblem and handlebars.

2.1.14 - Mar 4 2014

Minor Changes

  • Quick patch for previous JSHint fixes.

2.1.13 - Mar 4 2014

Minor Changes

  • mimosa-jshint now allows the .jshintrc to have comments. Previously it had to be 100% valid JSON and comments were not allowed.

2.1.12 - Mar 4 2014

Minor Changes

  • mimosa-require #30. Adds support for css plugin. Will not treat paths as javascript paths and will verify path exists in file system.

2.1.11 - Mar 3 2014

Minor Changes

  • Continuing to eliminate leading # in module placeholders.
  • mimosa-jshint has been updated to include the latest jshint. The latest jshint includes support for import 'foo' es6 module syntax.

2.1.10 - Feb 28 2014

Major Changes

  • mimosa #376. Fixed issue with duplicate template names being improperly reported.
  • mimosa #375. All of the mimosa new code, the command as well as the skeleton files, have been pulled into newmimosa and are brought into mimosa as a dependency.
  • New Module: mimosa-autoprefixer. Will automatically apply CSS vendor prefixes. Includes source map support.

2.1.9 - Feb 25 2014

Major Changes

  • New Skeleton: webapp. A basic web app skeleton for a require.js application without client libraries. Includes testing, minification of all assets and packaging.

Minor Changes

  • mimosa #369. Erroring out during mimosa build in a few more places, including in mimosa-require when files don't esprima parse correctly.
  • Continuing to eliminate leading # in module placeholders.

2.1.8 - Feb 24 2014

Minor Changes

  • mimosa #368. Fixed issue with 368 where web-package was not getting new default.

2.1.7 - Feb 23 2014

Major Changes

Minor Changes

  • mimosa #368. Updated mimosa-server to allow for server.js to be a default server.path. The code will now look for both server.coffee and server.js if a specific file path is not provided.
  • mimosa #368. mimosa new will no longer override server.path if JavaScript or TypeScript picked as transpiler.
  • mimosa-sass #2. Added includePaths as additional configuration option for mimosa-sass.

2.1.6 - Feb 22 2014

Major Changes

2.1.5 - Feb 22 2014

Major Changes

  • New Module: mimosa-stream-copy. Some files, like images or txt or font files, don't need to have anything done to them by any module. They just need to be copied from point A to point B. Source to public. mimosa-stream-copy will copy those files using super-fast streams and then stop the processing of those files. Copying didn't take a long time without streams, but with this module it takes no time at all.
  • New Module: mimosa-minify-img. This module adds a mimosa minimage command that will minify/optimize png, gif, jpg and jpeg files.

Minor Changes

  • Fixed issue with mimosa-require crashing on files not parsing properly

2.1.4 - Feb 20 2014

Major Changes

  • New Module: mimosa-eslint. An ESLint module allows for performing next gen static analysis.
  • mimosa-require #29. HUGE change for require.js users. mimosa-require will now use r.js' own esprima code to determine your dependencies and requirejs configuration. This will dramatically improve if not eliminate any false reports back from mimosa-require. Read more on the blog.

2.1.1, 2.1.2, 2.1.3 - Feb 15 2014

Major Changes

  • New Module: mimosa-emberscript. New JavaScript compiler for EmberScript. Includes creation of source maps.
  • New Module: mimosa-groundskeeper. A static analysis and code clean-up tool. This will remove things like console.log and debugger statements from your code as well as pragmas. This wraps the great groundskeeper tool and allows for all the same functionality.
  • mimosa-less #1, #2. Via a great PR, mimosa-less now support less source maps. Moar source maps ftw.

Minor Changes

  • Bumped JSHint to latest version to solve some issues with handling code output by EmberScript
  • mimosa #365. mimosa-require will now build r.js configs one step earlier in the mimosa workflows, from beforeOptimize to init, so that modules that tweak the r.js config before r.js is run can register for beforeOptimize safely and not have modules array order be an issue.
  • Bumped logmimosa version in skelmimosa package.

2.1.0 - Feb 12 2014

This release is entirely logging related.

Major Changes

  • Previous the logging config was under growl and the only configuration for logging related to when and if to send growl messages. That will be changing, so the root config object will now simple be logger. For a short period of time the old growl config will be deprecated but supported with the exception being the various onSuccess flags.
  • mimosa #355. The new logger config allows for Growl to be outright turned off. logger.growl.enabled.
  • mimosa #344. The new logger config allows for turning on/off info, warn, error, and success log levels.
  • mimosa #341. With 2.1 mimosa now places the logmimosa instance on the mimosa-config object that gets passed to all of the modules for registration and for workflow execution. It can be accessed at mimosaConfig.log.
  • All of the modules maintained by me (dbashford) have had their logmimosa dependency removed. Now all of those modules depend on the logmimosa that resides in Mimosa core. This will let Mimosa core maintain the single logger instance which now has much more dynamic configuration.
  • mimosa #336. The colorization of log messages has been changed dramatically. Previously the entire message was given a color. Now only a single ERROR, WARN, Debug, Info string at the beginning of the log message is colorized. Also, most messages had the key piece of the message wrapped in [[/]]. Now by default the brackets are stripped and the contents of the brackets are given a different color. The content of the brackets usually constituted an important piece of the message so it now draws focus. Additionally it the content inside the brackets contains a file path, the path is shortened to be relative to the root directory of the project. Previously it contained the absolute path. All color options are configurable if the colors set in the defaults do not do it for you.
  • The various growl onSuccess flags for javascript, css, etc are not being carried over to the new logger config. onSuccess will be a flag itself rather than an object.

Breaking Changes

  • All of the modules have been updated to use the latest logging functionality. The newest modules must be used with Mimosa 2.1 as the expect Mimosa to pass them the logger. Using the most up to date modules with older versions of Mimosa will result in errors.
  • Version 2.1 will work fine with older versions of modules except that the logging messages will bounce back and forth between the new logging (mimosa core 2.1) and the old logging (from the module)
  • If you were using (overriding) the growl.onsuccess flags, you'll find those flags are no longer available. They have been removed.

2.0.8 - Feb 6 2014

Major Changes

  • mimosa-sprite. mimosa-sprite now supports LESS and SASS output.

Minor Changes

2.0.7 - Feb 5 2014

This release just solved some problems with NPM not properly installing Mimosa.

2.0.6 - Feb 1 2014

Minor Changes

  • mimosa #356. Now registering coffeescript if coffeescript config file detected.

2.0.5 - Jan 31 2014

Minor Changes

  • mimosa-require #28. Fixed issue where the r.js optimize flag could not be overridden.
  • skelmimosa. Updated mod:list be more compact, view better with fewer columns. Updated dependencies.

External Module Updates

2.0.4 - Jan 28 2014

Major Changes

  • New Module: mimosa-handlebars-on-window. A dead simple module that will alter handlebars.js source slightly to attach Handlebars to the window object. Solves some current issues with Ember.js and r.js optimized builds. Also allows for managing Handlebars via Bower.

Minor Changes

  • mimosa #354. Added template.writeLibrary config to allow for not writing template libraries, like handlebars.js. By default Mimosa's template compiler functionality will write an AMD version of the client library.

2.0.3 - Jan 27 2014

Minor Changes

  • mimosa #353. Fixed issue with CSS compiler caused when name of folder included extension of compiler. For instance, normalize.styl/normalize.styl.

2.0.2 - Jan 27 2014

Minor Changes

  • skelmimosa #22. mimosa skel:new will now automatically clean up any .gitkeep files that might be laying around the skeleton.
  • mimosa #351. Fixed problem with mimosa new and folders that had both dashes and dots in the name, like /www.my-site.com/.

2.0.1 - Jan 26 2014

Major Changes

  • New Module: mimosa-generator. This module will transpile your ES6 generators down to valid ES5 javascript.

Minor Changes

  • mimosa-web-package #9. This PR to web-package allows config files to be outside the root of the distributed web package.
  • Fixed mimosa config help message.

2.0.0 - Jan 23 2014

Note: Some skeletons may take some time to be updated for the changes to 2.0. All skeletons at least have a pending pull request to make the needed changes.

With 2.0 all of Mimosa's compilers, which were previously internal to Mimosa, are now external in their own modules. So, for instance, this means there is now a mimosa-coffeescript module and a mimosa-stylus. All of the JavaScript transpilers, CSS proprocessors, micro-template compilers, and the copy "compiler" have their own Mimosa modules.

This shrinks Mimosa core's footprint by an enormous amount, making it quicker to npm install and easier to maintain. It also makes compilers easier to manage and update on their own while also making it much easier to add new compilers. Previously a new compiler would have been a PR to Mimosa core, now it can be a module on its own.

Huge Changes

  • All JS/CSS/Template compilers have been pulled out of Mimosa and into their own modules.
  • File copying support, for images or .js/.css files for example has also been pulled into its own module: mimosa-copy.
  • mimosa new received an overhaul that allows it to pull in needed compilers and build a mimosa-config based on those external modules.
  • The handlebars micro-template compiler was broken into two pieces, one for ember.js flavored handlebars and one for vanilla handlebars. Previously there was one compiler that supported both, but for ease of use they were broken out.
  • The compilers config has been eliminated. Previous the compilers config is how you would override the default extensions for a compiler or provide a specific compiler library (like a specific version of Handlebars) for Mimosa to use when compiling files. Both of these responsibilities now reside with the individual broken out compilers. All of the individual compilers now manage their own extensions and compiler library overrides.

Major Changes

  • All of the compilers are now written in JavaScript rather than CoffeeScript.
  • The mimosa-config generated by mimosa new will be a JavaScript file and be reduced down to only the needed config without comments. A 2nd file (called mimosa-config-documented.coffee) with all the comments for all of the modules will be generated at the same time.
  • mimosa config will now generate a mimosa-config-documented.coffee instead of a mimosa-config-commented.coffee.
  • mimosa new will no longer deliver Emblem assets. It will also not deliver Ember-Handlebars assets. Both of those require Ember and I rather mimosa new not be opinionated in that regard.
  • mimosa #348. An awesome PR provides support for multi-line SASS imports so that things like Foundation will compile out of the box without orphan file issues.

Minor Changes

  • mimosa #340. mimosa new can now handle absolute paths.
  • mimosa #333. mimosa-bower now ignores and removes from processing any packages that bower.paths cannot track down.
  • mimosa #277. mimosa-coffeescript and mimosa-iced-coffeescript both have been switched to the latest source map comment spec. See this thread for more details on the difference between conditional and non-conditional source maps. A configuration has been added to allow for switching back to conditional source maps if your browser does not support the latest spec.
  • mimosa-require #27. Fixed issue where mimosa watch + --optimize + template file change would not trigger a rebuild of r.js optimized files.
  • The mimosa-server module now depends on the installed node.js modules of your project for transpiler support. For example, if Mimosa is running your server and your server is written in CoffeeScript, you'll need to have coffee-script installed in your project. mimosa-server will look for it there. This only effects those running node servers in a language that needs to be transpiled.

You will need to... (Breaking Changes)

  • If you are using a JavaScript transpiler, a CSS proprocessor or a micro-templater, you will need to find the corresponding new Mimosa module and include it in your project by adding it to the modules array. For example, to include CoffeeScript and Stylus, add "coffeescript" and "stylus" to your modules array.
  • template.handlebars configuration has been removed/moved to the Handlebars and Ember-Handlebars compilers. If you have any specific template.handlebars config, you'll want to check the GitHub for those compilers to see how to move the config over.
  • If you provide specific configuration to any of your compilers, like stylus or template.handlebars, then when you include the new module for that compiler, take a second to review the README on that module's GitHub page for details about the configuration. All configuration has been preserved, but some of it has moved around.
  • If you have any files that need copying (rather than compiling), like .js or .css or images, then add "copy" to your modules array. The copying functionality was also broken out into its own module.
  • Have you provided any compilers configuration? You will have some changes to make as that configuration has been eliminated. All of the new compiler modules allow for overriding extensions and providing specific versions of a node compiler (like Handlebars). Check the documentation for the modules you use for more information.
  • Running a node.js server in a language other than JavaScript? You'll need to npm install that transpiler in order to get Mimosa to successfully start your server.
  • The Emblem compiler now only supports Ember.js based compilation. It is assumed if you are using Emblem that you are using Ember.

1.3.9 - Jan 11 2014

Minor Changes

  • mimosa #339. mimosa skel:new now handles absolute paths for the folder output and better cleans up after itself if something goes wrong.

1.3.8 - Jan 1 2014

Minor Changes

1.3.7 - Dec 31 2013

Minor Changes

  • mimosa #337. mimosa-server will now properly interpret iced-coffee-script server files on startup.

1.3.6 - Dec 31 2013

Big dependency/library upgrade release.

Minor Changes

  • mimosa #335. mimosa-bower will now put CoffeeScript files pulled in from a bower package into the javascript directory instead of the css directory.
  • Part of prepping for 2.0, all of the template compilers have been converted from CoffeeScript to JavaScript.
  • The underscore client library was updated to 1.5.2 from 1.5.1
  • The Ractive client library and the compiler were updated to 0.3.9
  • The Lodash client library was updated to 2.4.1
  • The Handlebars client library was updated to 1.2.0 and the compiler library was updated to 1.2.1
  • The Emblem compiler was updated to 0.3.6
  • The EJS compiler was updated to 0.3.6
  • The Dust client library and compiler have been updated to 2.2.2
  • Upgraded dependencies for mimosa new projects including Express.
  • mimosa-server dependencies bumped for Express, Jade and others.

1.3.5 - Dec 28 2013

Major Changes

  • New Skeleton: hyper. A minimal skeleton for using React.js in CoffeeScript via Hyper.

Minor Changes

  • Part of prepping for 2.0, all of the CSS and JavaScript compilers have been converted from CoffeeScript to JavaScript.
  • mimosa #332. The node flags that were made available in 1.3.2 have been added to the command line --help docs.

1.3.4 - Dec 23 2013

Minor Changes

  • mimosa #329. mimosa-server has a new property, packageJSONDir that points that module at your package.json. This is only valid for those projects that have their own server (as opposed to those using Mimosa's default server). mimosa-server will use your package.json to determine if there is a transpiler that needs to be required in before running your server. LiveScript for instance needs to be required in before the server can be started so that LiveScript files can be properly transpiled before being used.

1.3.3 - Dec 23 2013

Minor Changes

  • mimosa #330. Fixed bug introed in 1.3.1 that was causing plain .css files to occasionally not be compiled to compiledDir.

1.3.2 - Dec 20 2013

Major Changes

  • mimosa #315. Mimosa will now accept node flags upon startup. The list of available flags are --debug, --debug-brk, -gc, --expose-gc, --gc-global, --harmony, --harmony-proxies, --harmony-collections, --harmony-generators, and --prof.

Minor Changes

  • mimosa #327. To deconflict Mimosa's --debug and node's --debug, moved Mimosa from -D/--debug to -D/--mdebug.

1.3.1 - Dec 19 2013

Major Changes

  • New Skeleton: markdown-math. A simple skeleton for markdown and math.
  • New Skeleton: minimal-foundation. A skeleton with basic Foundation integration (only CSS) and Foundation intro template page.
  • mimosa #323. Updated CSS compilation so that included .css files will trigger proper CSS compiles. Now if a .css file is included in a Stylus or Less file, and that CSS file changes, the parent Stylus/Less file will be recompiled.

Minor Changes

  • mimosa #325. The copy "compiler" now has a 2nd setting for files not to copy. You could use the watch.exclude for this, but that prevents files from even being considered by Mimosa. The new copy.exclude does not prevent those files that were to be copied from being considered, it just prevents them from being copied. When would you want to process a copied file but not copy it? With mimosa #323 .css files can now trigger Stylus/Less recompiles. You may wish for a .css file to be processed so it can trigger that recompile, but you may not wish for that .css file to be copied itself.
  • mimosa #324. Better error messaging in default server when 404 occurs.
  • mimosa #320. Improved documentation for mimosa-client-jade-static to explain an idiosyncrasy of that module and optimization that results in the minify modules attempting to minify non javascript.
  • mimosa #319. Adjusted Mimosa's embedded server so that it would not throw errors when attempting to access certain bad URLs.
  • mimosa-testem-simple, mimosa-testem-require. The Testem version has been updated (from 0.4.2 to 0.6.1) for testem-simple and testem-require has the updated testem-simple. Testem has had a huge amount of updates since it was last updated, but a fundamental problem with folder/directory watching inside testem prevented the library from being updated. That issue has been fixed.
  • mimosa-jshint #2. Added globals support to jshint via PR.
  • mimosa-bower #33. Fixing some Windows path issues with custom path mapping.

1.3.0 - Dec 12 2013

1.3 marks the beginning of a total compiler rewrite. This first step, 1.3, has no impact on users but lays the ground work for pulling all of the compilers out of mimosa's core library and into external modules. That will take place as part of 2.0 which will likely follow a 2-4 weeks after 1.3.

No functionality or config changes for 1.3 from 1.2.4, but enough of the core has been rewritten to warrant bumping up a minor version.

1.2.4 - Dec 11 2013

Minor Changes

  • mimosa #322. Fixed issue with mimosa new + underscore/lodash micro templates.

1.2.3 - Dec 11 2013

Minor Changes

  • mimosa #321. Made adjustments to the regex for config replacement to fix config for mimosa new + no server.
  • mimosa-testem-simple #4. Added port setting which will allow for running both testem ci and testem at the same time without port collisions.
  • mimosa-testem-require. Bumped to contain the latest testem-simple.
  • mimosa-web-package #8. Check if server properties are present before using them. Fixes issue where if server config present but server module is not would cause build to hang/crash.

1.2.2 - Dec 4 2013

Minor Changes

  • mimosa #318. Added mp4 to the list of default copy.extensions.

1.2.1 - Nov 30 2013

Minor Changes

  • mimosa-bower #31. Improved error messaging and fixed issue where Mimosa would stop processing when Bower install would fail because of git not being detected.

1.2.0 - Nov 30 2013

Major Changes

  • mimosa-minify-css and mimosa-minify-js are now default modules.
  • mimosa-minify is no longer a default module
  • The only current Mimosa users that would be effected by this are those that are currently using the default module set (modules is commented out) and providing a minify.exclude config.
  • The current minify module will still be supported. If you are using it, it will still function.
  • For upgrade details visit the site.

1.1.10 - Nov 27 2013

Major Changes

  • New Module: mimosa-minify-css. This new module duplicates the CSS minification/cleaning functionality of the mimosa-minify module, omitting the CSS functionality. And it is written in JS rather than Coffee. With 1.2, this module will be one of two modules replacing the mimosa-minify module as Mimosa defaults.
  • New Module: mimosa-minify-js. This new module duplicates the JavaScript minification functionality of the mimosa-minify module, omitting the CSS functionality. And it is written in JS rather than Coffee. With 1.2, this module will be one of two modules replacing the mimosa-minify module as Mimosa defaults. Also, mimosa-minify did not create source maps for any files that didn't already have source maps, like compiled CoffeeScript files. This module will create source maps for all minified JavaScript files, whether they are transpiled files or not.

Minor Changes

1.1.9 - Nov 27 2013

Minor Changes

  • mimosa #314. mimosa new was not properly building the modules array for the mimosa-config when modules other than the internal build-ins were installed. Small typo.
  • mimosa-require #25. Adjusting comments in config placeholder.

1.1.8 - Nov 24 2013

Major Changes

  • A new configuration property was added to the root of the config: requiredMimosaVersion. It is null by default. When it is provided, Mimosa will force the specific version be installed to run Mimosa. This allows large project teams to force everyone to stay on a specific version, and to force them to upgrade in unison.
  • New Skeleton: minimal. A stripped down skeleton for quick startup. No server or prescribed MVC.

1.1.7 - Nov 23 2013

Minor Changes

1.1.6 - Nov 20 2013

  • mimosa #313. Fixed issue where Mimosa was not recognizing valid Stylus @import syntax without quotes.

1.1.5 - Nov 20 2013

Minor Changes

  • mimosa-live-reload #3. Added cross domain support to live reload.
  • mimosa-testem-require #7, mimosa-testem-simple #3. Killer PR added config flags for testem-require that allows for PhantomJS runs of testem to be turned off during mimosa watch and mimosa build. This lets testem-require just do the heavy lifting of setting up your application's testing suite but not do the execution.

1.1.4 - Nov 08 2013

Major Changes

  • mimosa #309. A new -e/--errorout flag was added to the build command. When the errorout flag is used, and a file fails compile (js, css, template), the build will exit immediately with a non-zero status. Use this flag for your automated builds. If errorout is not used, mimosa build will continue compiling files and will return a zero status.

1.1.2/1.1.3 - Nov 08 2013

Small patch fixes to fix problems with 1.1.1.

1.1.1 - Nov 07 2013

Minor Changes

  • mimosa #310. Fixed issue with mimosa-minify where .css files (not .styl or .scss etc) were not being minified on startup for mimosa watch or during mimosa build.

1.1.0 - Nov 04 2013

Two new modules, mimosa-jshint and mimosa-csslint, as of this release will replace the old mimosa-lint. This simplifies the config a good deal, and makes it much easier to remove one without removing the other.

mimosa-lint will still be supported, but as an external module. I won't be updating it all unless asked.

Details on how to upgrade on the site.

Major Changes

  • New Module: mimosa-jshint. A pure JSHint module. With release 1.1.0, this module replaces the JavaScript portion of the current mimosa-lint module as a default Mimosa module. It preserves all of the same functionality of the JS pieces of mimosa-lint, but with a simplified config. This module also allows those who were not interested in mimosa-lint's full feature set, but want JSHint, to add it by itself. See the site for details on how to configure this module.
  • New Module: mimosa-csslint. A pure CSSLint module. With release 1.1.0, this module replaces the CSS portion of of the current mimosa-lint module as a default Mimosa module. It preserves all of the same functionality of CSS pieces of mimosa-lint, but with a simplified config. This module also allows those who were not interested in mimosa-lint's full feature set but want CSSLint to simply add it. See the site for details on how to configure this module.
  • The two modules listed above are now default modules.
  • mimosa-lint is no longer a default module

Minor Changes

  • mimosa-post-hook. Updated the module to allow for configuring which postBuild workflow step to run the commands on. This'll allow you to, for instance, run some command before the server starts. Also added the ability to selectively choose when to continue Mimosa workflow processing for each command. This will allow you to wait for a timeout or a certain message in stdout before resuming Mimosa workflow steps. So, for example, you can ensure Mongo is started before starting the server.

Breaking Changes

  • If you have a commented out mimosa-config modules property, these two new modules will be activated. If you need a quick fix, uncomment your modules array and leave it unchanged. You will continue using the older lint module. Otherwise checkout the 1.1 Release information on the site to upgrade and use the new modules.
  • If you have uncommented your modules property, then you will be using whatever modules you have listed and no changes are necessary. To upgrade to the new lint/hint modules and stop using the previous one, checkout the 1.1 Release information on the site.

1.0.12 - Oct 31 2013

Major Changes

  • New Module: mimosa-spritesmith. From the community comes this fork of mimosa-sprite which shifts the spriting dependency to spritesmith and provides retina support. Great docs, check it out!

Minor Changes

  • Dependency updates: stylus, nib, less, iced-coffee, ractive, underscore, dust, emblem, jade. All updated to latest. Remember, if the latest versions don't work for you, you can always supply a specific version that works for you.
  • mimosa-combine #11. From a PR, addresses white spaces issues in combined files.

1.0.11 - Oct 30 2013

Minor Changes

  • mimosa #305. Adjustment to mimosa mod:config command to allow it to see locally installed modules. Previously if you had modules in a project's node_modules directory (as opposed to installed inside Mimosa itself, as with mimosa mod:install), mod:config would not be able to find them.

1.0.10 - Oct 30 2013

Minor Changes

  • mimosa #304, mimosa-testem-require #6. Allowing mimosa-config default config object settings to be null. Previously mimosa-config object properties had to be {}. Setting them to null would cause Mimosa to error out when the property needed to be overridden.

1.0.9 - Oct 28 2013

Major Changes

  • mimosa-bower #28. A new config setting, bower.copy.unknownMainFullCopy, is a quick fix for bower packages that do not declare a main. The right way to solve this problem is to set up a mainOverride that pulls out the specific files you want, but in lieu of that, this will simply copy the entire package into the appropriate place. It defaults to false.
  • New Module: mimosa-requirebuild-module-include. A module for including module dependencies into an r.js build.
  • New Module: mimosa-requirebuild-textplugin-module-include. Long, though descriptive, name for a new module that will add your text plugin dependencies to your requirejs modules config.

1.0.8 - Oct 21 2013

Major Changes

  • New Module: mimosa-post-hook. A module for executing scripts/commands when mimosa watch finishes its startup.
  • mimosa-require #24. Addressed some issues that popped up with the recent modules support. If running mimosa watch, you could only run optimization successfully one time when watch started up. Every subsequent run (after saving a file for instance) would error out. That has been addressed, however one of the pieces to fix this was to disable, by default, creation of source maps during modules-based r.js runs (non-modules runs will continue to have source maps). Even after addressing most of the issues, source maps still made it difficult to keep developing while mimosa watch was running. Source maps can be forced on using require.optimize.overrides, and they will work, but only that first time. Work will be done int he future to address source maps + modules dev, likely at the same time mimosa-require is updated to the latest requirejs.

Minor Changes

  • mimosa-sprite. Removed need to return object from options function. Also added debugging.
  • mimosa-require #24. mimosa clean will now properly clean up after modules runs.

1.0.7 - Oct 19 2013

Minor Changes

  • mimosa-live-reload #2. mimosa-live-reload would fail if attempting to write reload-client.js to the output folder if the output folder didn't exist. Now it'll create the folder if its not there.
  • mimosa-require #23. mimosa clean now does a better job of cleaning up over r.js runs involving a modules config.

1.0.6 - Oct 17 2013

Major Changes

  • New Module: mimosa-sprite. This module will generate CSS sprite images and corresponding stylesheets.

Minor Changes

  • mimosa #301. .css files were not being properly handled during mimosa watch after the initial startup. An update to a .css file would not update the file in the watch.compiledDir.

1.0.5 - Oct 17 2013

Minor Changes

1.0.4 - Oct 15 2013

Minor Changes

  • mimosa-require #22. Fixed a stray async call in the tracker code.
  • mimosa #296. Mimosa now shuts down the clean watcher after the cleaning is done. The clean watcher not being shut down meant that any files added (like from a bower install) after the cleaner was finished might get removed as soon as they are compiled to watch.compiledDir and you'd end up with randomly missing files.

1.0.3 - Oct 15 2013

Minor Changes

  • server-template-compile #3. Module now includes all the templating languages it needs rather than depending on other modules.

  • mimosa #295 and mimosa #292. PR included support for Stylus' include css functionality.

  • mimosa #293. Haven't fixed #293, but error messaging has been improved. mimosa mod:list will not work behind a proxy and previously the command would error out. Now there is some more helpful messaging.

  • mimosa #291. PR created support for the Stylus url function. Configuration pass through to the url functionality is available via stylus.url

    stylus:
      url:
        limit: 40000

1.0.2 - Oct 9 2013

Major Changes

  • New Skeleton: backbone-topcoat. New skeleton integrates some simple Backbone boilerplate with Top Coat. Coded in CoffeeScript/Stylus/Underscore with Hogan/Express on the server. Check it out!

Minor Changes

1.0.1 - Oct 8 2013

Major Changes

  • New Module: mimosa-plato. A module for running the Plato static analysis tool against your JavaScript.
  • New Module: mimosa-js-valiadte. Uses Esprima to catch validation and syntax errors in JavaScript. Great if you choose to not use a linter.

Minor Changes

  • mimosa-require. Fixed issue where regular non-optimized builds, mimosa build, would cause dependency checking to fail.

1.0.0 Final - Oct 8 2013

Minor Changes

  • mimosa-testem-require. Fixed issue with random diffs popping up in the test-variables file.
  • mimosa #271. mimosa-web-package now builds the proper tar command when using tools like git bash on windows. Previous it made a Windows cmd compatible command, now it goes *nix if using an emulator.

1.0.0-rc.7 - Oct 2 2013

Planning to release 1.0 Final on Monday Oct 7, but wanted to get the following updates in sooner than that.

Major Changes

  • New Example App: MimomsaDynamicRequire. A quick little example showing how to use Mimosa to build a requirejs app with dynamic modules.

Minor Changes

  • mimosa #287. Better error messaging out of mimosa-require when require.js paths config isn't proper.
  • mimosa #285. If no file of a given language needed to be compiled, then the compiler for that language would not be required in during startup. When the server file of that language was required in order to start the server, it could not be compiled. Now compiler libs are brought in whether or not a file needs to be compiled.
  • mimosa #283. Added a real 'none' server option to mimosa new that will legit not provide server options. Previously the 'none' option was actually Mimosa's embedded server rather than no server at all. The expectation is that you will point the watch.compiledDir to some public folder of yours.

1.0.0-rc.6 - Sept 23 2013

Major Changes

  • New Module: mimosa-es6-module-transpiler. Use ES6 module syntax today! This module will compile your ES6 module syntax down to AMD, CommonJS or globals.
  • mimosa #284. Enabling the new mimosa-require tracking functionality by default. Also updated the mimosa new .gitignore to exclude the tracking.json by default. Many .mimosa artifacts benefit from being in source control, but this file does not.
  • mimosa-require #21. mimosa-require can now gracefully handle r.js module setups. A new modules property has been added to require.optimize. When a modules array is provided, mimosa-require will alter the r.js run config appropriately.

1.0.0-rc.5 - Sept 16 2013

Major Changes

  • New Module: mimosa-require-lint. This module will determine if you have any unused AMD dependencies in your define callback or in your CommonJS code wrapped in the AMD CommonJS wrapper. In the future it may house other AMD related checks. If you have any ideas, open an issue!
  • New Skeleton: zappa-basic. A few people over the past few months have asked how to use a Zappa as a server, with live reload and such. So here ya go!
  • mimosa #281. mimosa mod:list has received an overhaul. It now shows all Mimosa modules from NPM. Installed modules are sorted to the top. Pass an -i/--installed to just see those you have installed. Calls to retrieve module information go to a Heroku app that caches the NPM information every hour. This removes npm as a dependency for Mimosa internally. mod:list will also inform you if you have an out of date dependency.
  • mimosa #281. The command mimosa mod:search has been dropped in lieu of simple improvements to mod:list mentioned above.

Minor Changes

  • mimosa-require #20. Much of mimosa-require is tailored to 1-main-to-1-output builds. But if a single run results in multiple outputs, mimosa-require had issues with messaging properly and with cleaning up the aftermath. That is fixed with this. Hoping to include more 1-run-many-output support soon.
  • mimosa-require #19. mimosa-require will now validate paths in packages config.
  • mimosa #282. Handling ./ at front of templates path alias resulting in wrong AMD path being written to templates.js.
  • mimosa #280. Programmatically setting dynamicSourceMaps to false if minify flag is used as Uglify cannot take dynamic source maps as input.
  • mimosa-import-source #5. Added a usePolling flag to config to help slow down CPU burn on Windows machines.

1.0.0-rc.4 - Sept 09 2013

Deprecating template.amdWrap as a config setting but still will support it in the short term. That is the only breaking-ish change in this release.

Huge Changes

  • New Module: mimosa-browserify. Until now Mimosa's CommonJS support has been via AMD wrapping and using RequireJS. With the addition of a browserify module, Mimosa can now boast full CommonJS support and another means besides r.js to bundle your applications. To support the browserify module, the change mentioned below regarding CommonJS support for templates was necessary. This closes the oldest open Mimosa ticket for CommonJS support.

Major Changes

  • New Skeleton: browserify-example. To show how to use the new browserify module @JonET whipped up a quick example project that takes the vanilla mimosa new app and converts it to use CommonJS/Browserify instead of AMD/RequireJS.
  • New Skeleton: ember-commonjs. A basic Ember app wired together using CommonJS. The skeleton will grow, but for now it shows how to configure Mimosa to use browserify and commonjs to create your Ember.js application.
  • mimosa #273. Mimosa now provides the option to output the combined template file as a commonjs module. The former amdWrap:true/false setting has been replaced with a wrapType setting that takes amd, common or none. Outputting a commonjs compliant templates files is the extent of the core Mimosa commonjs support. For instance, for now, Mimosa will not output a CommonJS compliant library file.
  • mimosa-bower #25. The bower:install command has changed. Previously it did exactly what mimosa bower did. It installed everything in the bower.json. Now it can be used to install new libraries. For example: mimosa bower:install backbone,lodash#1.2.1. Notice multiple can be installed by comma-delimiting them, and version numbers can be used. The result of this will be the libraries will be installed, but also the project's bower.json dependencies object will be updated. To update devDependencies instead, use the -d flag.

Minor Changes

  • mimosa-require. Made some updates to the tracking functionality released with rc.3. Tracked paths are now relative to watch.compiledDir instead of the root of the project. Path separators are normalized to unix style to avoid diffs cross-project. Also to prevent unnecessary file diffs, the tracking file object keys are sorted. Will probably enable tracking by default after another release.
  • mimosa-require #17. Issue with map validation addressed.

1.0.0-rc.3 - Sept 03 2013

Huge Changes

  • mimosa-require #14. Mimosa needed to have all of its JavaScript rebuilt with every startup so that mimosa-require could rebuild its dependency graph. With this release, mimosa-require is capable of tracking your project's dependency information between Mimosa runs. mimosa-require will persist to the file system the information it needs to startup without requiring all JavaScript files to be processed/compiled. A new tracking configuration has been added to the require config. When require.tracking.enabled is set to true, mimosa-require will keep track of dependency information on the file system.

    require.tracking.enabled defaults to false for now while this feature is new and still being worked out. It will default to true in the near future after its had some time to shake out.

    If files are moved or changed while Mimosa is not running, tracking may get out of sync. When this happens, run a mimosa clean and mimosa-require will rebuild its tracking information.

Major Changes

  • New Module: mimosa-coffeelint allows you to lint your coffeescript.

  • mimosa #273. By default Mimosa now outputs source maps as dynamic. So no .map or .src files are written, instead the map and source are base64 encoded and placed inside the JavaScript output. This means 66% less CoffeeScript related I/O and 66% fewer HTTP requests. Fewer HTTP requests also means less clutter in your debugger. Dynamic source maps also allow for tools like browserify to utilize the source maps as part of bundling.

    Both the coffeescript and iced configurations now have a sourceMapDynamic flag which defaults to true. Flip it back to false to go back to old multi-file source map support.

Minor Changes

  • mimosa-testem-simple now builds its list of spec files at the beginning of the workflow. To use mimosa-testem-require with rc.3 you will need version v0.6.5 of mimosa-testem-require, otherwise mimosa-testem-require may not properly discover spec files.
  • mimosa. Mimosa modules can now force Mimosa to run a clean at the beginning of mimosa watch starting up.

Upgrade Info / Breaking Changes

  • If you are using mimosa-testem-simple, you will want to make sure you upgrade to v0.6.5.

1.0.0-rc.2 - Aug 29 2013

Some possible breaking changes with how template paths are handled, so check out the breaking changes below.

Major Changes

  • mimosa #272. template paths are now relative to watch.sourceDir rather than watch.javascriptDir so template files can be placed outside of watch.javascriptDir and the template output files can go anywhere inside watch.sourceDir. This is possibly a breaking change. Previous defaults are preserved.

Minor Changes

Upgrade Info / Breaking Changes

  • You have no changes to make if you are not using any micro-templaters or did not override any of Mimosa's defaults.
  • If you were overriding the location of output files, you will need to alter the paths as the relative path has changed from watch.javascriptDir to watch.sourceDir
  • If you were providing folders to bundle into different output files, you will need to alter the paths as the relative path has changed from watch.javascriptDir to watch.sourceDir

1.0.0-rc.1 - Aug 27 2013

1.0 upgrade info below.

1.0! Real excited to get to this milestone. All of the built-in Mimosa modules have also been ticked up to 1.0.

Huge Changes

  • mimosa #254. mimosa-bower is now a default module. mimosa new will deliver a bower.json and not deliver jquery.js or require.js.

Major Changes

  • mimosa #268. The command mimosa mod:init has been removed from Mimosa. New Mimosa skeletons have been added for creating a JavaScript Mimosa module and a CoffeeScript Mimosa module. mimosa skel:new mimosa-module-javascript and mimosa skel:new mimosa-module-coffeescript
  • mimosa #268. Mimosa now comes with built-in support for the Ractive templating library. Two-way data binding ftw!
  • mimosa #258. Removed node-sass as a dependency as it occasionally breaks Mimosa installs. It also forces node v0.10. Mimosa still supports node-sass, but it needs to be provided to it via the compilers.libs.sass configuration parameter.
  • mimosa #256. All require calls for compilers are now delayed until the initial file of that type is encountered. This should slightly improve startup time, but it will also stop compiler confusion. Occasionally, for instance, iced-coffee-script would compile files on behalf of coffee-script.
  • mimosa #255. All compilers can now be provided via the mimosa-config by way of the compilers.libs setting. This allows users of Mimosa to use specific versions of compilers if Mimosa's current default versions aren't satisfactory.

Minor Changes

  • mimosa #259. Updated skeleton registry JSON, added details for future skeleton browsing web app front-end use.
  • mimosa-bower #22. mimosa-bower will now watch your bower.json and when changes to it occur, kick off a bower install.
  • All Mimosa modules

Upgrade Info / Breaking Changes

  • A minor inconvenience, and not very breaking, but if you have a Mimosa project that has not overridden the modules array, then when you upgrade to 1.0 bower will now be included in your project. You'll get a message indicating that a bower.json cannot be found. If you do not want Bower, simply uncomment the modules array and leave bower out.
  • template.handlebars.lib and template.emblem.lib have been moved to compilers.libs.handlebars and compilers.libs.emblem respectively.
  • Using node-sass? It is no longer bundled with Mimosa. To use node-sass you must npm install to install it into your project and then use compilers.libs.sass to require it in.