-
Notifications
You must be signed in to change notification settings - Fork 51
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
Broke because the meteor issue [1.3.3] import from absolute paths no longer work #7225 #51
Comments
I am seeing the same thing, yup. |
Replaced all absolute paths into relative path declarations. Right now it is not throwing any errors, but when I try to access the application through browser getting following errors on browser console:
|
It gives me those errors so right now I just reverted back to the old version which is working for me ( 1.3.0). If Git is used in the project, just run git stash save to revert recent changes. |
How did you do that exactly? When I change .meteor/release to 1.3.0 instead of 1.3.2.4 I get :
|
@martinhbramwell , is your project working property before you updated to 1.3.3? and are you using Git? If so, just use |
@junibrosas I just revert to 1.3.2.4 ( in .meteor/release ) and everything works fine. My question was about how you use 1.3.0 if it does not exist? |
I am also getting that. Show stopper. Back to 1.3.2.4 :-( |
@martinhbramwell try meteor update --release |
All I get is :
|
@martinhbramwell I read in following talk you have fixed this issue. Could you please share how you have fixed it? As I am getting same error if I upgrade to meteor 1.3.4.1. |
@gantu I described the steps to get to 1.3.4.1 in my first post in the "talk" you refer to. But here it is again (slightly edited) :
|
Thanks @martinhbramwell, these steps are fixing the issue. |
I tried to fix it by relative paths but still no luck :( .
The text was updated successfully, but these errors were encountered: