ember-data
Advanced tools
Comparing version 1.0.0-beta.10 to 1.0.0-beta.11
@@ -11,4 +11,4 @@ 'use strict'; | ||
afterInstall: function() { | ||
return this.addBowerPackageToProject('ember-data', '1.0.0-beta.10'); | ||
return this.addBowerPackageToProject('ember-data', '1.0.0-beta.11'); | ||
} | ||
}; |
{ | ||
"name": "ember-data", | ||
"version": "1.0.0-beta.10", | ||
"version": "1.0.0-beta.11", | ||
"namespace": "DS", | ||
@@ -51,5 +51,5 @@ "repository": "git://github.com/emberjs/data.git", | ||
"ember-publisher": "0.0.6", | ||
"testem": "^0.6.17", | ||
"testem": "^0.6.19", | ||
"yuidocjs": "~0.3.46" | ||
} | ||
} |
@@ -29,12 +29,12 @@ ## Ember Data [![Build Status](https://secure.travis-ci.org/emberjs/data.svg?branch=master)](http://travis-ci.org/emberjs/data) | ||
Similarly the latest passing build from the "beta" branch can be found | ||
Similarly, the latest passing build from the "beta" branch can be found | ||
on [http://emberjs.com/builds/#/beta](http://emberjs.com/builds/#/beta) | ||
You also have the option to build ember-data.js yourself. Clone the | ||
repository, run `broccoli build dist` after [setup](#setup). You'll find | ||
ember-data.js in the `dist` directory. | ||
Or build ember-data.js yourself. Clone the repository and run `npm run dist` | ||
after [setup](#setup). You'll find ember-data.js in the `dist` directory. | ||
#### Internet Explorer 8 | ||
If you need to support Internet Explorer, you will need to use es5-shim.js and es5-sham.js from [es5-shim](https://github.com/es-shims/es5-shim). | ||
If you need to support Internet Explorer, you will need to use es5-shim.js and | ||
es5-sham.js from [es5-shim](https://github.com/es-shims/es5-shim). | ||
@@ -41,0 +41,0 @@ ### Instantiating the Store |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
8009
1