I upgrading the references according the lodash v4 breaking changes:

import pairs from 'lodash/object/pairs'; to import toPairs from 'lodash/toPairs';

I also tried import { toPairs } from 'lodash';.

ReferenceError: lodash/_castPath.js: unknown node of type undefined with constructor "Function"

https://travis-ci.org/kellyselden/package-hint-historic-resolver/jobs/186700644#L654
https://github.com/kellyselden/package-hint-historic-resolver/pull/296/files

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository.

• WARN: Using npm packages for Renovate presets is now deprecated. Please migrate to repository-based presets instead.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): commitlint monorepo (patch) (@commitlint/cli, @commitlint/config-conventional, @commitlint/travis-cli)
• chore(deps): stable ember infrastructure (patch) (ember-cli-dependency-checker, ember-source)
• chore(deps): @ember/test-helpers
• chore(deps): @mike-north/js-lib-renovate-config
• chore(deps): ember-try
• chore(deps): stable ember infrastructure (major) (ember-cli, ember-qunit, ember-resolver, ember-source, eslint-plugin-ember)
• chore: lockfile maintenance
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): semantic-release [security]
• chore(deps): @ember/optional-features
• chore(deps): ember-cli-test-loader
• chore(deps): ember-maybe-import-regenerator
• chore(deps): ember-source-channel-url
• chore(deps): ember-try
• fix(deps): broccoli-funnel
• fix(deps): broccoli-merge-trees

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): @ember/test-helpers
• chore(deps): commitlint monorepo (major) (@commitlint/cli, @commitlint/config-conventional, @commitlint/travis-cli)

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

It's not working with ember-cli 1.13.13 due to dependencies :/

when i try to do that in the browser, i get this errors:

from command line i just get stuck and when i terminate i get this:

    ---
        message: >
            Received SIGINT signal

tried in:

• node v4.2.2/v5.3.0
• npm v2.14.10 / v3.5.2
• ember-cli 1.13.12

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.7.0 of broccoli-asset-rev was just published.

This version is covered by your current version range and after updating it in your project the build failed.

broccoli-asset-rev is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.7.0 of loader.js was just published.

This version is covered by your current version range and after updating it in your project the build failed.

loader.js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

We were getting strange issues:

yarn install v1.8.0
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
warning cs-core-api > ember-lodash > semantic-release > @semantic-release/npm > npm > [email protected]: this version has a breaking change. use 1.1.0 or upgrade to latest
error Couldn't find package "travis-deploy-once@^5.0.9" required by "@mike-north/[email protected]" on the "npm" registry.

Which lead me to question, why are the CI/deployment scripts part of the dependencies. Shouldn't they be moved to devDependencies?

Why not move to lodash 4.x?

Version 1.13.0 of greenkeeper-lockfile was just published.

This version is covered by your current version range and after updating it in your project the build failed.

greenkeeper-lockfile is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 2.1.1 of ember-cli-dependency-checker was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-dependency-checker is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 2.0.4 of ember-cli-htmlbars was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-htmlbars is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

We just tried to upgrade to the new version of ember-lodash and we had problem using it when executing in FastBoot.

The full stack trace error is as follows:

Error: Could not find module `lodash` imported from `athena/instance-initializers/fastboot/thrift`
    at missingModule (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:244:11)
    at findModule (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:255:17)
    at Module.findDeps (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:195:24)
    at findModule (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:258:11)
    at requireModule (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:25:15)
    at resolveInitializer (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:136572:18)
    at registerInstanceInitializers (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:136591:31)
    at exports.default (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:136612:5)
    at Module.callback (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/athena.js:286:41)
    at Module.exports (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:136:32)
    at Module._reify (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:169:59)
    at Module.reify (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:155:27)
    at Module.exports (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:134:10)
    at Object.requireModule (/Users/josemarluedke/Projects/Neighborly/demeter/main/dist/dev/fastboot/vendor.js:28:18)
    at Object.<anonymous> (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/fastboot/dist/cjs/ember-app.js:160:18)
    at VMSandbox.run (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/fastboot/dist/cjs/vm-sandbox.js:18:13)
    at EmberApp.createEmberApp (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/fastboot/dist/cjs/ember-app.js:159:30)
    at EmberApp.retrieveSandboxedApp (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/fastboot/dist/cjs/ember-app.js:184:17)
    at new EmberApp (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/fastboot/dist/cjs/ember-app.js:48:21)
    at FastBoot._buildEmberApp (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/fastboot/dist/cjs/index.js:111:17)
    at new FastBoot (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/fastboot/dist/cjs/index.js:52:10)
    at fastbootExpressMiddleware (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/fastboot-express-middleware/index.js:24:16)
    at exec.then (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/ember-cli-fastboot/lib/tasks/fastboot-server.js:34:71)
    at tryCatch (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/rsvp/dist/lib/rsvp/-internal.js:215:12)
    at invokeCallback (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/rsvp/dist/lib/rsvp/-internal.js:230:13)
    at publish (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/rsvp/dist/lib/rsvp/-internal.js:198:7)
    at flush (/Users/josemarluedke/Projects/Neighborly/demeter/main/node_modules/rsvp/dist/lib/rsvp/asap.js:85:5)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Version 4.3.0 of ember-cli-qunit was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-qunit is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

kinda depending on lodash/lodash#1704

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 6.12.0 of ember-cli-babel was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-babel is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

I develop an addon that depends on ember-lodash. It is used by an ember-cli application, so the dependency tree looks like this:

MyApp
  --  MyAddon
      -- ember-lodash

While trying to boot MyApp, an error is thrown inside ember-lodash's index.js file. The error arises while trying to evaluate this.project.addonPackages['ember-lodash'].path. The problem with trying to evaluate that is that this.project.addonPackages does not actually include ember-lodash--it is a dependency of MyAddon, not a dependency of MyApp.

$ ember s
version: 1.13.8
Cannot read property 'path' of undefined
TypeError: Cannot read property 'path' of undefined
    at Class.module.exports.treeForAddon (/Users/andre/src/plos/lemur-collections/frontend/node_modules/lemur-commons/node_modules/ember-lodash/index.js:11:74)
    at Class._treeFor (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/models/addon.js:330:31)
    at Class.treeFor (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/models/addon.js:300:19)
    at /Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/models/addon.js:253:32
    at Array.map (native)
    at Class.eachAddonInvoke (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/models/addon.js:251:22)
    at Class.treeFor (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/models/addon.js:298:20)
    at EmberApp.<anonymous> (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:358:20)
    at Array.map (native)
    at EmberApp.addonTreesFor (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:356:30)
    at EmberApp._addonTree (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:725:36)
    at EmberApp._processedVendorTree (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:789:29)
    at EmberApp._processedExternalTree (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:819:21)
    at EmberApp.appAndDependencies (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:906:30)
    at EmberApp.javascript (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:973:34)
    at EmberApp.toArray (/Users/andre/src/plos/lemur-collections/frontend/node_modules/ember-cli/lib/broccoli/ember-app.js:1346:10)

Version 4.17.5 of lodash-es was just published.

This version is covered by your current version range and after updating it in your project the build failed.

lodash-es is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Version 2.0.2 of ember-cli-uglify was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-uglify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 1.8.0 of ember-cli-inject-live-reload was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-inject-live-reload is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I'm trying to figure out if it's possible to use this library in my addon, but optionally not import lodash into the host app's final vendor.js. I use this in Ember CLI Mirage, which is primarily enabled in development/testing.

Is there a strategy I can take for a Mirage option be used at build-time to exclude lodash? I'm happy to PR once I have a better idea. My broccoli-fu is weak.

Version 2.18.1 of ember-source was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-source is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Is there something keeping me from using e.g. import { startsWith } from 'lodash/string';?

I just updated the ember-cli version in one addon and I can't make this addon work.

Repo: https://github.com/cibernox/ember-assign-helper/tree/allow-deep-merge
Steps:

• Install and run the tests. Should be green.
• Update ember-cli to 2.12.0-beta.1
• Run the tests. Tests fail now.

Any idea?

Error: ENOENT, no such file or directory '/app/node_modules/ember-lodash/node_modules/lodash-es'

This occurs because npm3 has a flat structure; there are no more nested node_modules directories. Now lodash-es lives on the top-level node_modules along with the main dependencies. As a result, we need a new way to load in the dependency for npm v3 users.

I've found that in many of my projects that I use ember-lodash, I end up writing Ember helpers that mostly just call a Lodash function and pass along arguments. For example:

// app/helpers/lodash-start-case.js

import Ember from 'ember';
import _string from 'lodash/string';

export function lodashStartCase([string]) {
    return _string.startCase(string);
}

export default Ember.Helper.helper(lodashStartCase);

This allows me to take advantage of Lodash transformations in my template (without having to make a CP):

<h1>{{lodash-start-case title}}</h1>

Would there be interest in a PR that adds some of these helpers to the addon?

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Version 2.18.1 of ember-cli was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I think we should align addon major version to lodash major version. So my current plan is to release a 3.0.0 and a 4.0.0 to allow for a clean upgrade.

@mike-north do you have any objections on this?

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 5.1.0 of eslint-plugin-ember was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-ember is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

i'm trying to install it on an addon.

I ran ember install ember-lodash

when I run ember s it throws

Can you please update the ember-cli-babel dependency so this module can be used with Node 8?
Currently it prevents installation due to:

error [email protected]: The engine "node" is incompatible with this module. Expected version "^4.5 || 6.* || 7.*".

This requires a --ignore-engines flag to install at present which is cumbersome.

In ember-cli version 2.11.0, the below import works earlier,
import findKey from 'lodash/object/findKey';
but after upgrading ember-cli to 2.13.3, it throws Error: Could not find module lodash/object/findKey`.

import { findKey } from 'lodash/object'; => this works
import { findKey } from 'lodash'; => this works
import findKey from 'lodash/object/findKey'; => this throws error.

I just upgraded to ember-cli v2.13.1 and use phantomjs v2.1.14, and now the qunit tests are failing during module loading. The Tests run fine in Chrome though.

I am using ember-lodash v4.17.2.

<error message="
Died on test #1 moduleLoadFailure@http://localhost:10001/assets/test-support.js:15093:28
http://localhost:10001/assets/test-support.js:15321:33
require@http://localhost:10001/assets/test-support.js:15309:32
loadModules@http://localhost:10001/assets/test-support.js:15301:23
loadTests@http://localhost:10001/assets/test-support.js:15146:33
start@http://localhost:10001/assets/test-support.js:15181:16
http://localhost:10001/assets/tests.js:1194:28
exports@http://localhost:10001/assets/vendor.js:119:37
requireModule@http://localhost:10001/assets/vendor.js:34:25
global code@http://localhost:10001/assets/tests.js:1262:8: Object is not a constructor (evaluating '(0, _lodash_defineProperty['default'])')
">

Version 1.1.0 of ember-load-initializers was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-load-initializers is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.5.1 of ember-resolver was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-resolver is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

shouldn't the description for the repo be updated? I think what is now is outdated and misleading

Consider also to add topics to the repo (recent feature from github)

thanks

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Hi! Thanks for getting lodash usable with imports.

We're currently on ember 2.17, ember-lodash 4.17.6

EDIT: tl;dr the version of broccoli-concat-analyser I was using was calculating the compressed size incorrectly. Turns out it's not 144KB, it's more like 68KB. But still much larger than ~24KB, which is what I expected.

I was checking out our addon weight (using broccoli-concat-analyser) to find some low-hanging fruit to slim down vendor.js and noticed lodash taking up more space than I expected!

lodash is showing as ~144kb uglified + compressed, but lodash.com says the Full build (~24kB gzipped).

Maybe we're doing something incorrectly here? I tried using https://github.com/kellyselden/ember-cli-tree-shaker but it didn't do much, like ~4kb savings from our production build 😢
Any help would be greatly appreciated. Even if you could quickly try a production build using broccoli-concat-analyser and let me know if lodash shows as 144kb for you as well or smaller

Now that there exists something like https://github.com/ef4/ember-auto-import, is there need to have an ember specific npm package for lodash ?