v3.0.0-rc.8

Ok guys, for anyone following along with the v3 journey still, thank you. We've come a long way, and it's been a huge amount of work. Little did I think when I started the v3 branch that it would be over 270 commits, but here we are, and we're easily pushing over that. We are learning a lot in the process and making steady progress towards a stable public release. Some changes this pre-release:

• Lots of bugfixes, most importantly a small regression in when that was causing a permissions error was patched.
• Deployments are here! I sunk about a month into ship, our library for deployment, and it's at a pretty good place with amazon s3, heroku, and github pages. On top of that, the heroku and github pages deployer have no external dependencies -- that's right, not even git. I spent some time looking, and was unable to find anyone else who had built a library to deploy to either heroku or github without git. We're even riding on heroku's edge api in order to return streaming build status messages.
• A ton of work went into architecture that will allow us to multiple roots' compile speed by many orders of magnitude, but sadly we couldn't get it to a place where things were entirely stable and plugins were working for this release. This is a very challenging issue, and something we will continue working hard on until it is solved.

If you are just a bystander, we would love for you to get involved with helping to evaluate and test v3. It's pretty stable at this point, and has been used in full builds at carrot, so you are safe to try it out! Thanks for following and reading 💖

v2.1.4

• node-sass version updated
• new project generation creates parent directories if they don't exist
• infestor version locked, preventing a bug with served files

v3.0.0-rc.7

Good news guys, roots is getting lots more stable, it's officially over 1000 commits, and we're quickly nearing the point where it's ready for public release - whoo! 🎉

You can install this release with npm i roots@pre

A bunch of changes in this last release:

• Lots of changes to the roots public api, making it more stable, better tested, and easier to use. All roots methods now return promises, which fulfill, reject, and even emit progress events for long running processes like new.
• Huge refactor to the CLI, now based on argparse which clears the way for more flexible aliases, provides help docs for every command, and makes the cli much more solid. As a result, the cli is covered by tests at 100%
• roots clean command is now present and working
• All code is linted by coffeelint now automatically as part of the test suite. No more little mistakes slipping by over here
• We now have way more stylish badges in the readme as well as a svg logo for extra swag. Top secret roots v3 branding and marketing materials are also in development and on the way
• If you pass a path to the write_hook that contains a directory that doesn't exist, it's now automatically created for you. Whoo!
• More and better handling for extension errors, clear messaging of almost any mistake you could make when developing extensions and very thorough test coverage for each of these cases
• The long-neglected manpage has been updated to be accurate
• All dependencies updated to the latest versions
• project_hooks.after extension hook added, thanks to @dapetcu21 for this wonderful feature
• node_modules added to watcher ignores, vastly reducing CPU usage on roots watch - thanks to @Olivier-G for finding this
• watcher does not bail if there's a compile error, keeps watching and removes the error message if you fix the error
• charge implemented as roots' new server, adding better test coverage and fantastic capabilities to roots' local server like single page app redirects, tight cache control, and clean urls
• Roots' first ever integration test is now included in the test suite and running on travis, which tests the browser functionality by opening a new project, changing files, and ensuring that the page reloads and errors appear.
• A small bugfix allows extensions to modify locals much more accurately, making the dynamic content extension much more powerful without making anything more complex.

v3.0.0-rc.6

As the number of prereleases increases, so does the stability of roots v3! A bunch of changes in this one:

• Public API updated to be cleaner and more efficient
• Fixed a bug in which package.json files with no dependencies caused an error #421
• Added a setup function to extensions with which extensions can perform any async setup necessary
• CLI refactored, stabilized, and tested, docs updated
• roots watch --no-open will now not auto-open the browser
• roots clean now works
• roots new has seen a bunch of great updates with the next version of sprout

Look forward to another prerelease soon including bugfixes, an even more stable CLI, sprout namespacing, and more!

v2.1.3

If you are following roots development, it's no secret that version 2.x is not in active development right now, although 3.x is very active. However, there have been a few little updates for those still using version 2.x that are being pushed with this release, including:

• jquery removed from reload assets
• a number of internal changes for those working on core
• better error handling in some cases #370
• cleaner livereload script injection
• allow pure css imports to stylus #427

Version 3 is coming very close to feature parity, so look forward to a huge release with a bunch of fantastic updates soon!

v3.0.0-rc.5

• Adds support for environments
• Fixes a bug where some languages (like markdown) were not correctly compiling
• Fixes an issue where special character in filenames are encoded

v3.0.0-rc.4

• Fixed a bug causing the watcher/livereload not to work correctly
• Major refactor of the extension API, makes everything much easier
• Huge update to extension docs
• Lots more tests and smaller bugfixes

v3.0.0-rc3

A bugfix release, closes out a bunch of issues we found while using the rc.2 release. Mainly:

• File and directories with periods in the name do not screw things up now #384 #402 #403
• Images and other non-utf8 files compile through properly #398 #408
• Full support for unicode characters both in files and filenames #400
• Default template now namespaced as roots-base
• Moar tests, better coverage
• A shiny and wonderful new documentation system that looks great, works on desktop and mobile, rebuilds automatically each push, and is tightly versioned, so you can view the docs at the time of any release.

Note: If you have been actively using the prereleases for some reason, run roots tpl reset after installing this one to avoid any errors with creating new projects.

v3.0.0-rc.2

While I truly thought that the rc1 release was great, it actually was pretty badly borked, which is my fault if we're being honest. Thank god for prereleases right? I have hopefully learned from my mistakes with this followup release though, and in all testing, things look to be performing nicely. There are also a number of really importance enhancements to the core codebase.

• Super thorough jsdoc documentation for almost every class and function
• Major extension API changes such that context is cleared every compile pass
• Better testing and smoother interface for the extension write hooks
• Files without extensions still compile through
• Empty folders are removed from the output
• The library is now compiled to javascript before publish and (hopefully) still works correctly

In addition, the officially maintained client-templates and dynamic-content extensions have been updated to work smoothly with the new extensions api, and each will have a new release soon!

v3.0.0-rc.1

Early prerelease for roots v3, which has been in the works for quite a bit. v3 is a full rewrite of roots, which comes along with significant architectural changes, cleaner and better code, much quicker speed, and more extensibility.

Only install this prerelease if you want to experiment around. Some basic docs are included in the docs folder, but these have quite a bit to go before this is ready for public release.

That being said, if you have been following roots closely and/or work with one of the core team members directly, this might be a good thing to try out. Client-side templates and dynamic content should be working if you include them correctly.

Stay tuned for more and more polished and stable releases out of v3!