Skip to content
This repository has been archived by the owner on Mar 22, 2019. It is now read-only.

Ember 2.12 blog post #2824

Merged
merged 1 commit into from
Mar 19, 2017
Merged

Ember 2.12 blog post #2824

merged 1 commit into from
Mar 19, 2017

Conversation

locks
Copy link
Contributor

@locks locks commented Mar 8, 2017

Ship approvals

Checklist

  • Ember
    • Blog
    • v2.12.0
    • v2.13.0-beta.1
  • Ember Data
    • Blog
    • v2.12.0
    • v2.13.0-beta.1
  • Ember CLI
    • Blog
    • v2.12.0
    • v2.13.0-beta.1

@acorncom
Copy link
Contributor

acorncom commented Mar 9, 2017

@locks Looks like the preview link here isn't quite accurate for Netlify?

@locks locks force-pushed the emberjs-release-2-12-0 branch from 04efd6f to 07a2298 Compare March 9, 2017 11:23
@locks locks changed the title Create 2017-03-13-ember-2-12-released.md Ember 2.12 blog post Mar 10, 2017
This public API replaces the intimate API of `_lookupFactory`, and additionally
discourages developers from setting properies on classes returned from the
container. For more information about this API see the [API
docs](http://emberjs.com/api/classes/ContainerProxyMixin.html#method_factoryFor)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This documentation URL has no content, needs to be written per TODOs in the issue description.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be good as of emberjs/ember.js#15005

to a point in browsing history. See pull request [#14011](https://github.com/emberjs/ember.js/pull/14011)
for more details.

For more details on the upcoming changes in Ember.js 2.12, please review the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be Ember.js 2.13 ? and should it point to the 2.13 beta 1 instead of 2.12?


#### Deprecations in Ember Data 2.13

There are no planned deprecations for Ember Data 2.12.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ember Data 2.12 --> Ember Data 2.13

There are no planned deprecations for Ember Data 2.12.

For more details on the upcoming changes in Ember Data 2.11, please review the
[Ember Data 2.12.0-beta.1 release page](https://github.com/emberjs/data/releases/tag/v2.12.0-beta.1).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above.


### Upcoming Changes in Ember.js 2.13

Building on the addition of `featureFor` in Ember 2.12, Ember 2.13 will change
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/featureFor/factoryFor/ ?

@mixonic
Copy link
Member

mixonic commented Mar 18, 2017

@bmac this is good to go? What about stable and beta releases?

@Turbo87 I think we're waiting on Ember-CLI blog content? What about beta and stable releases?

@bmac
Copy link
Member

bmac commented Mar 18, 2017

Ember Data is good to go.

@Turbo87
Copy link
Member

Turbo87 commented Mar 18, 2017

@mixonic I was under the impression that @locks and @rwjblue were working on the CLI part

@rwjblue
Copy link
Member

rwjblue commented Mar 18, 2017

Confirm

The latest beta of ember-cli-babel@6 takes advantage of the new `project.targets` API along with [babel-preset-env](https://github.com/babel/babel-preset-env)
to allow applications to have significantly better control of exactly what is transpiled. `babel-preset-env` utilizes the [caniuse](http://caniuse.com/) and
[@kangax]'s [ES6 compatibility database](https://kangax.github.io/compat-table/es6/) to know which features are available natively and which
require transpilation. For example, with the proper targets configuration ember-cli-babel will no longer transpile `cosnt` / `let`,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cosnt => const

@mixonic mixonic force-pushed the emberjs-release-2-12-0 branch 2 times, most recently from 74c70a2 to 923c6cf Compare March 19, 2017 19:12
@mixonic mixonic force-pushed the emberjs-release-2-12-0 branch from 2a22dc1 to 55d9851 Compare March 19, 2017 19:28
@mixonic mixonic merged commit 367b459 into master Mar 19, 2017
@mixonic mixonic deleted the emberjs-release-2-12-0 branch March 19, 2017 19:31
introduces roughly 19MB to a freshly generated application's `node_modules` size. As the `npm` client has become more stable (3.x series and
newer) this has seemed more and more wasteful.

Starting with Ember CLI 2.12, `npm` is no longer a dependency of. If a suitable version of `npm` is present on the system,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

of can be removed

As of Ember CLI 2.11 a new application has no dependencies via `bower.json`. This means the dependency on `bower` itself is also potential bloat.
Having `bower`
as a dependency added roughly 21MB to a new application's total `node_modules` size. In Ember CLI 2.12, bower is only added as a dependency if a command
requires `bower` and it is not already installed globally.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that is actually wrong, since we can't take advantage of globally installed bower

Thanks to [@hjdivad](https://github.com/hjdivad) for proposing and implementing this feature. Please read through [the RFC](https://github.com/ember-cli/rfcs/blob/master/complete/0091-addon-instrumentation-experimental-hooks.md)
for more details.

#### Target
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Targets?

@Turbo87
Copy link
Member

Turbo87 commented Mar 19, 2017

damn, merged while I was reviewing... 😄

@mixonic
Copy link
Member

mixonic commented Mar 19, 2017

@Turbo87 ah thanks, I will open another PR

@mixonic mixonic mentioned this pull request Mar 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants