Merge pull request #1902 from less/2_0_0

2.0.0 Pull Request

.gitignore

@@ -13,6 +13,7 @@ npm-debug.log
 # project-specific
 tmp
 test/browser/less.js
+test/sourcemaps/**/*.map
 test/sourcemaps/*.map
 test/sourcemaps/*.css
 

.jshintrc

@@ -5,7 +5,9 @@
     "node": true,
     "undef": true,
     "unused": "vars",
+    "trailing": true,
     "noarg": true,
     "eqnull": true,
-    "forin": true
+    "forin": true,
+    "predef": ["Promise"]
 }

.npmignore

@@ -1 +1,9 @@
 .gitattributes
+build/
+.grunt/
+benchmark/
+test/
+# re-include test files as they can be useful for plugins that do testing
+!test/*.js
+tmp/
+gradle/

CHANGELOG.md

@@ -1,3 +1,24 @@
+# 2.0.0-b1
+
+2014-10-19
+
+ - Public Beta / Release Candidate - Feedback welcome
+   For a guide to breaking changes see [the v2 upgrade guide](lesscss.org/usage/#v2-upgrade-guide)
+ - no longer including old versions of less in the repo or npm
+ - not including test less and gradle files in npm
+ - colours now output in the format they are added unless compressing, so yellow will output yellow, not its hex counterpart
+ - better parsing - better comment support and comments in brackets can now contain comments including quotes.
+ - Removal of dependency on clean-css - install less-plugin-clean-css and use --clean-css to reference plugin
+ - Environment Support - less is now separate from its node and browser environment implementations and adding support for another javascript environment should be straight forward.
+ - Plugin Support - it is now straight forward to add AST manipulations (see less-plugin-inline-images), file managers (see less-plugin-npm-import) and post processors (see less-plugin-clean-css and less-plugin-autoprefix).
+ - We now recommend using less.render and using the parser directly is not in the same way as in v2. It is possible but it would require changes and we do not guarantee it will not be broken in minor version releases.
+ - In the browser, less.pageLoadFinished will be a promise, resolved when less has finished its initial processing. less.refresh and less.modifyVars also return promises.
+ - In the browser, as before less is used as options, however this is now copied to less.options if you need to access after less has run
+ - In the browser, the cache can be overwritten by setting less.cache before less loads. After load less.cache will be the default implementation.
+ - less.js now uses browserify to generate its browser side component
+ - default values for the sourcemap options have been re-done and improved to hopefully mean creating sourcemaps is easier
+ - Many smaller bugfixes and API changes. Please let us know if something you relied on has disappeared or an area should be better documented.
+
 # 1.7.5
 
 2014-09-03
@@ -31,7 +52,7 @@
  - Do not round the results of color functions, like lightness, hue, luma etc.
  - Support cover and contain keywords in background definitions
 
-# 1.7.2
+ # 1.7.2
 
 2014-06-19
 

CONTRIBUTING.md

@@ -1,20 +1,20 @@
 # Contributing to Less.js
 
-> We welcome feature requests and bug reports. Please read these guidelines before submitting one. 
+> We welcome feature requests and bug reports. Please read these guidelines before submitting one.
 
 
 <span class="warning">**Words that begin with the at sign (`@`) must be wrapped in backticks!** </span>. As a courtesy to avoid sending notifications to any user that might have the `@username` being referenced, please remember that GitHub usernames also start with the at sign. If you don't wrap them in backticks, users will get unintended notifications from you.
 
-GitHub has other great markdown features as well, [go here to learn more about them](https://help.github.com/articles/github-flavored-markdown).   
+GitHub has other great markdown features as well, [go here to learn more about them](https://help.github.com/articles/github-flavored-markdown).
 
 
 ## Reporting Issues
 
-We only accept issues that are bug reports or feature requests. Bugs must be isolated and reproducible problems that we can fix within the Less.js core. Please read the following guidelines before opening any issue. 
+We only accept issues that are bug reports or feature requests. Bugs must be isolated and reproducible problems that we can fix within the Less.js core. Please read the following guidelines before opening any issue.
 
 1. **Search for existing issues.** We get a lot of duplicate issues, and you'd help us out a lot by first checking if someone else has reported the same issue. Moreover, the issue may have already been resolved with a fix available.
 2. **Create an isolated and reproducible test case.** Be sure the problem exists in Less.js's code with [reduced test cases](http://css-tricks.com/reduced-test-cases/) that should be included in each bug report.
-3. **Test with the latest version**. We get a lot of issues that could be resolved by updating your version of Less.js. 
+3. **Test with the latest version**. We get a lot of issues that could be resolved by updating your version of Less.js.
 3. **Include an example with source.** E.g. You can use [less2css.org](http://less2css.org/) to create a short test case. 
 4. **Share as much information as possible.** Include operating system and version. Describe how you use Less. If you use it in the browser, please include browser and version, and the version of Less.js you're using. Let us know if you're using the command line (`lessc`) or an external tool. And try to include steps to reproduce the bug.
 5. If you have a solution or suggestion for how to fix the bug you're reporting, please include it, or make a pull request - don't assume the maintainers know how to fix it just because you do.
@@ -32,15 +32,15 @@ Please report documentation issues in [the documentation project](https://github
 
 _Pull requests are encouraged!_
 
-* Start by adding a feature request to get feedback and see how your idea is received. 
+* Start by adding a feature request to get feedback and see how your idea is received.
 * If your pull request solves an existing issue, but it's different in some way, _please create a new issue_ and make sure to discuss it with the core contributors. Otherwise you risk your hard work being rejected.
 * Do not change the **./dist/** folder, we do this when releasing
-* _Please add tests_ for your work. Tests are invoked using `grunt test` command. It will run both node.js tests and browser ([PhantomJS](http://phantomjs.org/)) tests. 
+* _Please add tests_ for your work. Tests are invoked using `grunt test` command. It will run both node.js tests and browser ([PhantomJS](http://phantomjs.org/)) tests.
 
 ### Coding Standards
 
 * Always use spaces, never tabs
-* End lines in semi-colons. 
+* End lines in semi-colons.
 * Loosely aim towards jsHint standards