Upgrading to Meteor 0.9.1 troubles (broke the application for a long time)
I am having serious problems after updating meteor to 0.9.1.
Here are some examples of console errors.
Uncaught TypeError: undefined is not a function -- in dynamic_template.js
Uncaught TypeError: Cannot read property ‘prototype’ of undefined -- in helpers.js
Uncaught TypeError: undefined is not a function -- in router.js
Uncaught TypeError: Cannot read property ‘RouteController’ of undefined -- in iron-router-progress.js
Uncaught TypeError: Cannot read property ‘RouteController’ of undefined -- in global-imports.js
And dozens of: Uncaught ReferenceError: Template is not defined
- in client js files, both hardcopy created by me and the apparently ephemeral files that the meteorite seems to create on the fly.
And less than dozens: Uncaught ReferenceError: Meteor is not defined
- in files of the same type.
And one: Uncaught ReferenceError: Spacebars is not defined
- in login_buttons_dialogs.html
And about 10 sockjs errors on GET — net:ERR_CONNECTION_REFUSED
I cannot help thinking that either something very simple was not done during the upgrade procedure, or there are some very simple and widespread changes that need to be made to my code in order for it to run 0.9.1.
Create an app that is an extension and morphology of the microscope app. This is not rocket science at the moment. It worked last night before the update. This was 0.9.0.1 before the update.
Any help and understanding is greatly appreciated.
source to share
Thanks for the guidance. Everything looks good now. This is what I did:
I created a new meteor app, removed the 2 default packages and then added: bootstrap iron: router MRT: accounts-ny-boot-up-account-dropdown-password MRT: iron-router-progress Sacha: spin
Then I copied the files from the broken app to the new app and viola 'it worked.
I see that the directory structure and its naming conventions have been changed, colons instead of dashes in multiple spaces, and pointer or namespace prefixes like mrt, iron and sacha.
Here is an unexpected thing. I used to have a folder with package names that had a folder for each package containing all of its files. Now this folder is empty but still working. I am clearly informed about some things.
Again, thanks for the guidance. Even though it was pain, I see that the changes that arise must take place.
Best, Alex
source to share
Many packages break at Meteor@0.9.1 , I suggest you create a new Meteor app like:
$ meteor create --release 0.9.0 app
$ cd app
$ meteor remove insecure
$ meteor remove autopublish
and then add all packages you need with meteor add packagename
and copy all files from your application.
Stick with Meteor@0.9.0 until you know you can safely upgrade!
source to share