From 59507cba27f448b974b66fbd84448421c69ed063 Mon Sep 17 00:00:00 2001 From: Jessica Jordan Date: Thu, 18 Jul 2019 12:24:02 +0200 Subject: [PATCH 1/8] blog(embertimes#107): add section on ember auto import configs --- .../2019-07-19-the-ember-times-issue-107.md | 71 ++++++++++++------- 1 file changed, 46 insertions(+), 25 deletions(-) diff --git a/source/2019-07-19-the-ember-times-issue-107.md b/source/2019-07-19-the-ember-times-issue-107.md index 19311ea8e..1907f3e86 100644 --- a/source/2019-07-19-the-ember-times-issue-107.md +++ b/source/2019-07-19-the-ember-times-issue-107.md @@ -1,12 +1,12 @@ --- title: The Ember Times - Issue No. 107 -author: the crowd +author: Jessica Jordan, the crowd tags: Recent Posts, Newsletter, Ember.js Times, Ember Times, 2019 alias : "blog/2019/07/19-the-ember-times-issue-107.html" responsive: true --- - Emberistas! 🐹 +What's happening, Emberistas? 🐹 @@ -15,7 +15,7 @@ responsive: true ## [Section Title in Title Case 🐹](#section-url) - + @@ -24,7 +24,7 @@ responsive: true ## [Section Title in Title Case 🐹](#section-url) - + @@ -33,64 +33,85 @@ responsive: true ## [Section Title in Title Case 🐹](#section-url) - + - + --- -## [Section Title in Title Case 🐹](#section-url) - - - - - - +## [Custom Configuration of Ember Auto Import for Your Project 🐹](https://github.com/ef4/ember-auto-import/tree/v1.3.0#customizing-build-behavior) + +The useful addon [Ember Auto Import](https://emberobserver.com/addons/ember-auto-import) helps you to use third-party JavaScript libraries in your Ember app easily by providing a **zero-config import** mechanism for **npm** modules. + +You can [configure the addon to fit your project's specific needs](https://github.com/ef4/ember-auto-import#customizing-build-behavior). By providing the `autoImport` configuration object in your app options defined in `ember-cli-build.js`, you can, f.e., change the name of the packages to import from or exclude packages to be imported with Ember Auto Import, which you might have already provided to your app in another way. + +If you're already an avid user of Ember Auto Import (or plan to become one), be aware that from version 1.4.0+ the addon will **no longer include** Webpack's polyfills for a set of Node.js globals and modules automatically. [When upgrading to a version of the addon beyond 1.4.0](https://github.com/ef4/ember-auto-import#i-upgraded-my-ember-auto-import-version-and-now-things-dont-import-what-changed) you might see errors such as `global is not defined` popping up in your app or test suite. This might indicate that some of the packages included in your app may - even though they're run in a browser environment - still rely on globals that are usually only available in a Node environment and that these might require a polyfill to work correctly. See also [this issue on the Ember Auto Import repo](https://github.com/ef4/ember-auto-import/issues/218) for more context. + + +If you want to opt-in to these Node polyfills using Ember Auto Import, you can [configure them accordingly](https://github.com/ef4/ember-auto-import/issues/224#issuecomment-503400386) via the `autoImport` options in your `ember-cli-build.js`: + +``` +// ember-cli-build.js +let app = new EmberApp(defaults, { + autoImport: { + webpack: { + node: { + Buffer: false, + global: true, + process: true, + }, + } + } +}); +``` + +You can review the configuration defaults for the Node.js polyfill over at [the documentation for Webpack itself](https://webpack.js.org/configuration/node/#node). + --- ## [Section Title in Title Case 🐹](#section-url) - + - + --- ## [Section Title in Title Case 🐹](#section-url) - + - + --- ## [Section Title in Title Case 🐹](#section-url) - + - + --- ## [Section Title in Title Case 🐹](#section-url) - + - + --- ## [Section Title in Title Case 🐹](#section-url) - + - + --- ## [Contributors' Corner 👏](https://guides.emberjs.com/release/contributing/repositories/) @@ -112,7 +133,7 @@ responsive: true --- -## [#embertimes 📰](https://blog.emberjs.com/tags/newsletter.html) +## [#embertimes 📰](https://blog.emberjs.com/tags/newsletter.html) Want to write for the Ember Times? Have a suggestion for next week's issue? Join us at [#support-ember-times](https://discordapp.com/channels/480462759797063690/485450546887786506) on the [Ember Community Discord](https://discordapp.com/invite/zT3asNS) or ping us [@embertimes](https://twitter.com/embertimes) on Twitter. @@ -124,4 +145,4 @@ That's another wrap! ✨ Be kind, -the crowd and the Learning Team +Jessica Jordan, the crowd and the Learning Team From 62bc1c461d8e85cfba8b239b22130cc4f2aa1cc0 Mon Sep 17 00:00:00 2001 From: Jessica Jordan Date: Thu, 18 Jul 2019 12:26:53 +0200 Subject: [PATCH 2/8] blog(embertimes#107): add contributors + intro sentence --- source/2019-07-19-the-ember-times-issue-107.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/source/2019-07-19-the-ember-times-issue-107.md b/source/2019-07-19-the-ember-times-issue-107.md index 1907f3e86..135f438b0 100644 --- a/source/2019-07-19-the-ember-times-issue-107.md +++ b/source/2019-07-19-the-ember-times-issue-107.md @@ -8,7 +8,8 @@ responsive: true What's happening, Emberistas? 🐹 - +This week: +flexible imports with **Ember Auto Import** ⏬, --- @@ -116,7 +117,7 @@ You can review the configuration defaults for the Node.js polyfill over at [the ## [Contributors' Corner 👏](https://guides.emberjs.com/release/contributing/repositories/) -

This week we'd like to thank our siblings for their contributions to Ember and related repositories! 💖

+

This week we'd like to thank @kratiahuja, @dnalagatla, @kiwiupover, @bekzod, @chancancode, @dependabot-preview[bot], @elwayman02, @ursm, @pete-the-pete, @sivakumar-kailasam, @loganrosen, @mansona, @choheekim, @locks, @jenweber and @toddjordan for their contributions to Ember and related repositories! 💖

--- From f55c422e9d5b6c475ac12af0024f52efcfc05ded Mon Sep 17 00:00:00 2001 From: Jessica Jordan Date: Thu, 18 Jul 2019 14:20:13 +0200 Subject: [PATCH 3/8] Update source/2019-07-19-the-ember-times-issue-107.md Co-Authored-By: Isaac Lee <16869656+ijlee2@users.noreply.github.com> --- source/2019-07-19-the-ember-times-issue-107.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/2019-07-19-the-ember-times-issue-107.md b/source/2019-07-19-the-ember-times-issue-107.md index 135f438b0..b5b99daa2 100644 --- a/source/2019-07-19-the-ember-times-issue-107.md +++ b/source/2019-07-19-the-ember-times-issue-107.md @@ -42,7 +42,7 @@ flexible imports with **Ember Auto Import** ⏬, ## [Custom Configuration of Ember Auto Import for Your Project 🐹](https://github.com/ef4/ember-auto-import/tree/v1.3.0#customizing-build-behavior) -The useful addon [Ember Auto Import](https://emberobserver.com/addons/ember-auto-import) helps you to use third-party JavaScript libraries in your Ember app easily by providing a **zero-config import** mechanism for **npm** modules. +[Ember Auto Import](https://emberobserver.com/addons/ember-auto-import), a very useful addon, helps you easily use third-party JavaScript libraries in your Ember app by providing a **zero-config import** mechanism for **npm** modules. You can [configure the addon to fit your project's specific needs](https://github.com/ef4/ember-auto-import#customizing-build-behavior). By providing the `autoImport` configuration object in your app options defined in `ember-cli-build.js`, you can, f.e., change the name of the packages to import from or exclude packages to be imported with Ember Auto Import, which you might have already provided to your app in another way. From 1d0da83b14ea627dfc86f457f7abdd5bdcbd6c36 Mon Sep 17 00:00:00 2001 From: Jessica Jordan Date: Thu, 18 Jul 2019 14:20:38 +0200 Subject: [PATCH 4/8] Update source/2019-07-19-the-ember-times-issue-107.md Co-Authored-By: Isaac Lee <16869656+ijlee2@users.noreply.github.com> --- source/2019-07-19-the-ember-times-issue-107.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/2019-07-19-the-ember-times-issue-107.md b/source/2019-07-19-the-ember-times-issue-107.md index b5b99daa2..b197020a4 100644 --- a/source/2019-07-19-the-ember-times-issue-107.md +++ b/source/2019-07-19-the-ember-times-issue-107.md @@ -44,7 +44,7 @@ flexible imports with **Ember Auto Import** ⏬, [Ember Auto Import](https://emberobserver.com/addons/ember-auto-import), a very useful addon, helps you easily use third-party JavaScript libraries in your Ember app by providing a **zero-config import** mechanism for **npm** modules. -You can [configure the addon to fit your project's specific needs](https://github.com/ef4/ember-auto-import#customizing-build-behavior). By providing the `autoImport` configuration object in your app options defined in `ember-cli-build.js`, you can, f.e., change the name of the packages to import from or exclude packages to be imported with Ember Auto Import, which you might have already provided to your app in another way. +You can [configure the addon to fit your project's specific needs](https://github.com/ef4/ember-auto-import#customizing-build-behavior). By providing the `autoImport` configuration object in your app options defined in `ember-cli-build.js`, you can, for example, change the name of the packages to import from or exclude packages to be imported with Ember Auto Import, which you might have already provided to your app in another way. If you're already an avid user of Ember Auto Import (or plan to become one), be aware that from version 1.4.0+ the addon will **no longer include** Webpack's polyfills for a set of Node.js globals and modules automatically. [When upgrading to a version of the addon beyond 1.4.0](https://github.com/ef4/ember-auto-import#i-upgraded-my-ember-auto-import-version-and-now-things-dont-import-what-changed) you might see errors such as `global is not defined` popping up in your app or test suite. This might indicate that some of the packages included in your app may - even though they're run in a browser environment - still rely on globals that are usually only available in a Node environment and that these might require a polyfill to work correctly. See also [this issue on the Ember Auto Import repo](https://github.com/ef4/ember-auto-import/issues/218) for more context. From 63554d774aa15259da8fc73e622f5fabbf7aaab4 Mon Sep 17 00:00:00 2001 From: Jessica Jordan Date: Thu, 18 Jul 2019 14:21:27 +0200 Subject: [PATCH 5/8] Update source/2019-07-19-the-ember-times-issue-107.md --- source/2019-07-19-the-ember-times-issue-107.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/2019-07-19-the-ember-times-issue-107.md b/source/2019-07-19-the-ember-times-issue-107.md index b197020a4..d59ae9bb0 100644 --- a/source/2019-07-19-the-ember-times-issue-107.md +++ b/source/2019-07-19-the-ember-times-issue-107.md @@ -40,7 +40,7 @@ flexible imports with **Ember Auto Import** ⏬, --- -## [Custom Configuration of Ember Auto Import for Your Project 🐹](https://github.com/ef4/ember-auto-import/tree/v1.3.0#customizing-build-behavior) +## [Custom Configuration of Ember Auto Import for Your Project ⏬](https://github.com/ef4/ember-auto-import/tree/v1.3.0#customizing-build-behavior) [Ember Auto Import](https://emberobserver.com/addons/ember-auto-import), a very useful addon, helps you easily use third-party JavaScript libraries in your Ember app by providing a **zero-config import** mechanism for **npm** modules. From 91a3aab92d377d30b3c9ff958de9f2500b8b2040 Mon Sep 17 00:00:00 2001 From: Jessica Jordan Date: Thu, 18 Jul 2019 14:27:21 +0200 Subject: [PATCH 6/8] Update source/2019-07-19-the-ember-times-issue-107.md Co-Authored-By: Isaac Lee <16869656+ijlee2@users.noreply.github.com> --- source/2019-07-19-the-ember-times-issue-107.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/2019-07-19-the-ember-times-issue-107.md b/source/2019-07-19-the-ember-times-issue-107.md index d59ae9bb0..74c6f277a 100644 --- a/source/2019-07-19-the-ember-times-issue-107.md +++ b/source/2019-07-19-the-ember-times-issue-107.md @@ -46,7 +46,9 @@ flexible imports with **Ember Auto Import** ⏬, You can [configure the addon to fit your project's specific needs](https://github.com/ef4/ember-auto-import#customizing-build-behavior). By providing the `autoImport` configuration object in your app options defined in `ember-cli-build.js`, you can, for example, change the name of the packages to import from or exclude packages to be imported with Ember Auto Import, which you might have already provided to your app in another way. -If you're already an avid user of Ember Auto Import (or plan to become one), be aware that from version 1.4.0+ the addon will **no longer include** Webpack's polyfills for a set of Node.js globals and modules automatically. [When upgrading to a version of the addon beyond 1.4.0](https://github.com/ef4/ember-auto-import#i-upgraded-my-ember-auto-import-version-and-now-things-dont-import-what-changed) you might see errors such as `global is not defined` popping up in your app or test suite. This might indicate that some of the packages included in your app may - even though they're run in a browser environment - still rely on globals that are usually only available in a Node environment and that these might require a polyfill to work correctly. See also [this issue on the Ember Auto Import repo](https://github.com/ef4/ember-auto-import/issues/218) for more context. +If you're already an avid user of Ember Auto Import (or plan to become one), be aware that from version 1.4.0+ the addon will **no longer include** Webpack's polyfills for a set of Node.js globals and modules automatically. + +[When upgrading to a version of the addon beyond 1.4.0](https://github.com/ef4/ember-auto-import#i-upgraded-my-ember-auto-import-version-and-now-things-dont-import-what-changed), you might see errors such as `global is not defined` in your app or test suite. This might indicate that some of your packages—even though they run in a browser environment—still rely on globals (these are usually only available in a Node environment) and may require a polyfill to work correctly. You can check [this issue on the Ember Auto Import repo](https://github.com/ef4/ember-auto-import/issues/218) for more context. If you want to opt-in to these Node polyfills using Ember Auto Import, you can [configure them accordingly](https://github.com/ef4/ember-auto-import/issues/224#issuecomment-503400386) via the `autoImport` options in your `ember-cli-build.js`: From fe6c86e5115d2a548c8d176e4eb780c426be5ada Mon Sep 17 00:00:00 2001 From: Jessica Jordan Date: Thu, 18 Jul 2019 14:42:03 +0200 Subject: [PATCH 7/8] blog(embertimes#107): address comments from review --- source/2019-07-19-the-ember-times-issue-107.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/2019-07-19-the-ember-times-issue-107.md b/source/2019-07-19-the-ember-times-issue-107.md index 74c6f277a..cd3442d10 100644 --- a/source/2019-07-19-the-ember-times-issue-107.md +++ b/source/2019-07-19-the-ember-times-issue-107.md @@ -42,7 +42,7 @@ flexible imports with **Ember Auto Import** ⏬, ## [Custom Configuration of Ember Auto Import for Your Project ⏬](https://github.com/ef4/ember-auto-import/tree/v1.3.0#customizing-build-behavior) -[Ember Auto Import](https://emberobserver.com/addons/ember-auto-import), a very useful addon, helps you easily use third-party JavaScript libraries in your Ember app by providing a **zero-config import** mechanism for **npm** modules. +[Ember Auto Import](https://emberobserver.com/addons/ember-auto-import), a very useful addon, helps you easily **import** and use third-party JavaScript libraries from **npm** in your Ember app. You can [configure the addon to fit your project's specific needs](https://github.com/ef4/ember-auto-import#customizing-build-behavior). By providing the `autoImport` configuration object in your app options defined in `ember-cli-build.js`, you can, for example, change the name of the packages to import from or exclude packages to be imported with Ember Auto Import, which you might have already provided to your app in another way. From 20b2213ba017f17004277d1b74d26ccf0691a151 Mon Sep 17 00:00:00 2001 From: Jessica Jordan Date: Thu, 18 Jul 2019 14:49:36 +0200 Subject: [PATCH 8/8] blog(releases): fix travis build --- source/2018-07-02-ember-3-2-released.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/2018-07-02-ember-3-2-released.md b/source/2018-07-02-ember-3-2-released.md index 546790929..123935104 100644 --- a/source/2018-07-02-ember-3-2-released.md +++ b/source/2018-07-02-ember-3-2-released.md @@ -6,7 +6,7 @@ responsive: true alias : "blog/2018/06/29/ember-3-2-released.html" --- -Today the Ember project is releasing version 3.2.0 of Ember.js, Ember Data, and Ember CLI- a little later than planned, for sure! Thank you for your support and patience. +Today the Ember project is releasing version 3.2.0 of Ember.js, Ember Data, and Ember CLI- a little later than planned, for sure! Thank you for your support and patience. This release kicks off the 3.3 beta cycle for all sub-projects. We encourage our community (especially addon authors) to help test these beta builds and report any bugs before they are published as a final release in six weeks' time. The [ember-try](https://github.com/ember-cli/ember-try) addon is a great way to @@ -84,6 +84,7 @@ Use of `Ember.Logger` is deprecated. You should replace any calls to `Ember.Logg In Microsoft Edge and IE11, uses of console beyond calling its methods may require more subtle changes than simply substituting console wherever `Logger` appears. In these browsers, they will behave as they do in other browsers when the development tools are open. + But, when run normally, calls to its methods must not be bound to anything other than the console object. If not, you will receive an Invalid calling object exception. This is a known inconsistency with these browsers. To avoid this, transform this: