Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

use app.import instead of browserify

See original GitHub issue

looks like in ember-cli v2.9 or 2.10 there is a new way for importing amd modules

app.import('vendor/a-file-from-the-folder-above.js', {         
   using: [{ transformation: 'amd', as: 'some-package' }]        
});

I wonder if we can use it instead of browserify and npm:* syntax

cc @MiguelMadero

Issue Analytics

State:
Created 7 years ago
Comments:13 (4 by maintainers)

Top GitHub Comments

1reaction

aaminevcommented, Oct 25, 2016

@MiguelMadero keep in mind that there are another packages, like redux-thunk or redux-logger, both contain dist folder though, so should be the same.

0reactions

MiguelMaderocommented, Nov 30, 2016

He did a good summary 😃

On Wed, Nov 30, 2016 at 2:49 PM Dustin Farris notifications@github.com wrote:

ember-cli-node-modules-to-vendor got a ringing endorsement from ember-browserify

kellyselden/ember-cli-node-modules-to-vendor#2 (comment) https://github.com/kellyselden/ember-cli-node-modules-to-vendor/issues/2#issuecomment-263337894

We can probably reopen this issue

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/toranb/ember-redux/issues/28#issuecomment-263990925, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC5HPHJnEZPSIfFDU9FPWwJpS3LbyWzks5rDeFNgaJpZM4KfeAQ .