Quick fix for compatibility with Meteor 0.6 #162

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
3 participants
@logankoester

#161

This was actually all it took to fix the problem for me.

@sbking

This comment has been minimized.

Show comment Hide comment
@sbking

sbking Apr 5, 2013

Is the requireHack still necessary in 0.6.0? Looks like it could be refactored to just use Npm.require().

sbking commented Apr 5, 2013

Is the requireHack still necessary in 0.6.0? Looks like it could be refactored to just use Npm.require().

@logankoester

This comment has been minimized.

Show comment Hide comment
@logankoester

logankoester Apr 5, 2013

That's how it looked at first to me too, but it seems to also solve some problems related to the meteor package being located in a subdirectory of the same npm module, which I'm afraid I don't fully understand.

That's how it looked at first to me too, but it seems to also solve some problems related to the meteor package being located in a subdirectory of the same npm module, which I'm afraid I don't fully understand.

@bminer

This comment has been minimized.

Show comment Hide comment
@bminer

bminer Apr 8, 2013

Owner

The Blade smart package will be restructured for Meteor 0.6.0. That stupid hack is FINALLY no longer necessary. :)

I'm closing this pull request for now. I will address this in the next release of Blade. :)

Thanks anyway for the pull request. Much appreciated!

Owner

bminer commented Apr 8, 2013

The Blade smart package will be restructured for Meteor 0.6.0. That stupid hack is FINALLY no longer necessary. :)

I'm closing this pull request for now. I will address this in the next release of Blade. :)

Thanks anyway for the pull request. Much appreciated!

@bminer bminer closed this Apr 8, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment