Ember-intl: Cannot build, due to test-support trying to be bundled with my app?

Created on 17 Aug 2018  路  8Comments  路  Source: ember-intl/ember-intl

  • [ x ] I am on the latest ember-intl version
  • [ x ] I have searched the issues of this repo and believe that this is not a duplicate

Environment

  • Ember Version: 49e58e45604bd63ac1001cb491195c032c050053
  • Ember CLI Version: 0f9d15d011fd9adb4c2a8db52e44bf5d74679631
  • Ember Intl Version: 3.1.1
  • Browser(s): n/a
  • Node Version: 8.11.3

Steps to Reproduce

Clone this repo: https://gitlab.com/NullVoxPopuli/emberclear/

run cd packages/frontend; yarn build:production

Get error:

Build failed.
Build Error (Bundler)

bundleForPath("ember-intl/test-support/-private/pick-last-locale.js") returned tests" but the only configured bundle names are app
dependency issue requires research

Most helpful comment

Fix upstream in ember-auto-import resolves the original issue, feel free to reopen if you're still having issues after upgrading. Thanks @ef4!

All 8 comments

Unclear to me why you're hitting this.

I'm also using 3.1.1 in prod and haven't encountered this. May be an issue with another one of your dependencies (tree shaking perhaps?). I'll need to spend time looking into what the cause is but it may be outside of ember-intl's control.

@buschtoens any ideas?

fwiw, I'm using module unification. :-\

but also, @ef4 said it was an issue with ember-auto-import https://github.com/ef4/ember-auto-import/issues/105

which has a known issues with canary.

so, maybe once _that's_ resolved, this can will also be resolved?

Okay I'll treat this as a dependency bug and will keep an eye out for the solve.

Given what we are leveraging auto import for(lodash util methods), we can consider removing it temporarily.

@NullVoxPopuli yes, https://github.com/ef4/ember-auto-import/issues/105 was breaking your situation. But there is no other known issue with canary -- the one you reported a long time ago was resolved.

I don't think this is an issue with ember-cli canary, as I'm encountering it while using [email protected], [email protected], and [email protected]. I was able to work around it by downgrading from version 1.2.11 to 1.2.10 of ember-auto-import.

I also commented on https://github.com/ef4/ember-auto-import/issues/110 since I saw that other people had filed an issue that matched mine there.

Edit: my issue is now fixed in 1.2.12 of ember-auto-import. It might not be the same as this issue, though, so disregard my comment if it's not helpful.

At this point, I don't have any known ember-auto-import bugs that would be relevant to ember-intl, so if you are still having trouble please file a new issue.

Fix upstream in ember-auto-import resolves the original issue, feel free to reopen if you're still having issues after upgrading. Thanks @ef4!

Was this page helpful?
0 / 5 - 0 ratings