-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meteor 0.5.9 project seems to be ran with meteor 0.6 #15
Comments
@Xyand -- is there any chance you could take a look at this? Basically it'd be better if the package used |
I wish to add that using @nate-strauser's version locked on mrt 0.5.1 solved my issue |
Good. Can you provide a link here so people have some way of running pre-0.6.0 meteorite on heroku for now? |
https://github.com/nate-strauser/heroku-buildpack-meteorite (mentioned here #13 (comment)) |
@emirotin, Please check if this one works for you: https://github.com/Xyand/heroku-buildpack-meteorite |
@Xyand nope, throws
@nate-strauser's version still works |
This should be fixed now. |
I have a project locked on Meteor 0.5.9, from my smart.json:
It heavily relies on variable sharing across files (thanks to their concatenation) - the thing that changed in 0.6. That's why I cannot instantly migrate (and don't want to actually).
My local versions (work ok)
Last time I deployed to Heroku it went OK as well - it was 5 days ago.
Today after deploy I start getting errors related to variables not defined.
In the deployment log I see
Though it installs v0.5.9 it feels like the code is ran with 0.6.0
Also the's — don't know if related
The text was updated successfully, but these errors were encountered: