dbashford / mimosa

A lightning-fast, modular, next generation browser development tool.
http://mimosa.io/
519 stars 34 forks source link

Weird logging with Ember.js and Require.js #411

Closed xypaul closed 9 years ago

xypaul commented 10 years ago

Anything I can do to get rid of these annoying messages?

screen shot 2014-10-15 at 2 58 50 pm

Thanks in advance :+1:

dbashford commented 10 years ago

Ember has it's own little internal module system and that is tripping you up.

If ember was inside your vendor directory, as defined in your mimosa config, it would stop doing that.

Sent from my iPhone


On 2014-10-15 11:03:36 +0000 Paul Knittel notifications@github.com wrote:

Anything I can do to get rid of these annoying messages?

screen shot 2014-10-15 at 2 58 50 
pm

Thanks in advance :+1:


Reply to this email directly or view it on GitHub: https://github.com/dbashford/mimosa/issues/411

dbashford commented 10 years ago

This may be a good excuse to whip up a derequire module, eh @brzpegasus? ;)

brzpegasus commented 10 years ago

That wouldn't be a bad idea. I know they were trying to address this issue for 1.8 by running derequire on Ember itself so this wouldn't be a problem anymore. But the derequire module could still be helpful for anyone unable to upgrade. Wait, was I just volunteered? =)

dbashford commented 10 years ago

Lol, not really, however, it would probably be easy to whip together.

If I wasn't banging my head against sass source maps...

dbashford commented 9 years ago

So as of the latest Ember, Ember 1.8, the defines and requires have been removed and replaced with enifeds and eriuqers.

Given that, I think I'll close this out. mimosa-require won't ding internal defines when they aren't defines anymore. =)

If you (or anyone else) can't upgrade, let me know and I'll look at putting a derequire module together.