components/ember-data

Shim repository for EmberJS's Data component.

Components

Package manager-friendly distributions of many popular Components.

Note: Components is NOT a package manager.

What is it

There are many packages managers... More than one for each language! And for each one you need a mirror repository with built *.js.

Components is here to centralize this, having only one repository by project, supporting every package manager there is and keeping project repositories up-to-date.

Keep it simple: all Components repositories will be made available in the official list of your package manager (naming may change based on said manager): you don't have to do anything, just install our component like any other.

When we can extend the package manager, Components comes with some additionnal features (the install directory for example).

Package Managers

Although package manager support varies from package to package, Components aims to support as many package managers as possible. Some examples include:

• npm
• Bower
• Component
• Jam
• volo
• Ender
• Composer, see Components Installer for Composer
• Package Manager Comparison

Notes

The Bower repositories try to have a standardized name of components-*.

Maintainers

If you are using grunt as part of the build process for your library, you can use this helper to release a new version of your library in the main repo, and the compiled version of your code to your component repository:

https://github.com/walmartlabs/grunt-release-component

Contributing

If you see a Component that requires an update, or is missing support for a certain package manager, feel free to open an issue or better, a pull request!

ember-data's Issues

name in `package.json`

(Follow up on a Slack question, see https://embercommunity.slack.com/archives/-help/p1483056261019192)

Is there a particular reason to use the name components-ember-data in package.json?

I want to use ember-data in ember-try scenarii but unfortunately, the Ember team does not currently update dist-tags in npm. Renaming the package in this repo's package.json (if possible) would be a great leverage to achieve this. I will detail at length as necessary.

[Issue] Ember-Data 2.8.0 not tagged

This is a problem because services like https://cdnjs.cloudflare.com rely on the tags. So specifically because there is no 2.8.0 tag, there is no ember-data 2.8.0 on cdnjs, which in turn causes issues for ember-twiddle (can't use ember-data 2.8 because we use cdnjs to download ember and ember-data files)

Include Ember Data 0.14

Some of us are using Ember Data 0.14 (the last version before Ember Data 1.0).
It would be really helpful to include it.

Bower: ember-data marked as incompatible with ember 1.2

After 0386da8 bower marks ember versions > 1.0 as incompatible. ~1 was allowing ember 1.2.0.

> bower -v
1.2.8

Canary branch is empy

The canary branch is empty. What happened to the canary builds?

Publish to NuGet.

• Need to add .nuspec file.
• Need permissions to push updates for @fivetanley and @rjackson.
• Need to add upload of new package to publishing process.

/cc @ntotten

Missing #release

The release branche has no data for 2.15
It looks like the master branch has been used by mistake?

Fail to install with Bower

Seems to be trying to make a new directory in a path that doesn't exist.

ember-data.js.map isn't being updated on cdnjs.com

ember-data.js.map isn't being updated with the other ember-data.js files on https://cdnjs.com

https://cdnjs.cloudflare.com/ajax/libs/ember-data.js/1.0.0-beta.18/ember-data.js.map is actually for 1.0.0-beta.16.1, not 1.0.0-beta.18. Similarly, 1.0.0-beta.17 is also using the map from 1.0.0-beta.16.1.

I opened cdnjs/cdnjs#4692, but it was closed as an issue from "upstream". Is this the right place?

Thanks for any help.

@fivetanley

Fix Bower/Component/NPM support

Is "ember-data" the right name of the component?
If you look for "ember" in http://sindresorhus.com/bower-components/ , you see a ember-data already exists. "ember" matches that from components/ember though.

move ember dependency into optionalDependencies

having ember in the dependencies forces a npm install of the components repo to have a duplicate install of ember. If someone is installing ember/ember-data via the components shim library, their package.json will have to look something like this

    "components-ember": "https://github.com/components/ember/archive/2.4.2.tar.gz",
    "components-ember-data": "https://github.com/components/ember-data/archive/2.4.0.tar.gz",
    "ember": "https://github.com/emberjs/ember.js/archive/v2.4.2.tar.gz"

The ember library is currently incompatible with npm, which is the whole reason for using the shims.

An alternative would be to have the 'components-ember' repo in the dependencies key.

Error while install via composer

Part of require-dev:

...
"components/ember": "dev-master",
"components/ember-data": "dev-master"
...

Result is:

Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for components/ember-data dev-master -> satisfiable by components/ember-data[dev-master].
    - components/ember-data dev-master requires components/ember 1.* -> no matching package found.

If we change ember's version to 1.*@dev installation will be successfully but with ember 1.4.0.

1.13 release problems

1. bower.json hasn't been updated.
2. The source maps haven't been updated.

Latest beta and canary distributions don't contain ember-data.js.map

We're using the following ember-try configs for the simplabs/ember-simple-auth tests:

{
  name: 'ember-beta',
  dependencies: {
    'ember': 'components/ember#beta',
    'ember-data': 'components/ember-data#beta'
  },
  resolutions: {
    'ember': 'beta',
    'ember-data': 'beta'
  }
},
{
  name: 'ember-canary',
  dependencies: {
    'ember': 'components/ember#canary',
    'ember-data': 'components/ember-data#canary'
  },
  resolutions: {
    'ember': 'canary',
    'ember-data': 'canary'
  }
}

The latest beta and canary branches don't contain the ember-data.js.map file though, causing Ember CLI to fail with:

ENOENT, no such file or directory '/home/travis/build/simplabs/ember-simple-auth/tmp/funnel-input_base_path-r4FlWJx6.tmp/0/bower_components/ember-data/ember-data.js.map'

See the travis build for reference: https://travis-ci.org/simplabs/ember-simple-auth/builds/91904720

Beta tag is empty

components/ember-data#beta is empty

Ember namespace version still shows up as '1.0.0-beta.2'

Although this release is labeled by its bower.json as 1.0.0-beta.3, the source still says it's '1.0.0-beta.2' in the default, minified, and production versions. It appears the source has indeed been updated, as per 2ebef08 -- however, the version itself has, for some reason, stayed the same.

is missing release branch