If you want to take advantage of code splitting and dynamic importing, then yes, you will have to put some time into refactoring your application to do so. But that's not Meteor specific, it's just how life is.
I guess Meteor does so much out of the box, you might forget it can't (not yet, at least) write your app for you!
The main takeaway from this should be: your Meteor 1.0 project from many moons ago will still run on Meteor 1.8.1 (the latest recommended release). There is no need to refactor anything. During the evolution from 1.0to 1.8.1 Meteor has gained all kinds of great new features, fixes and improvements, but they are, at least to my knowledge, 99% non-breaking and/or optional. That's quite something.
That sounds right. Sure, you obviously may need to update structure to use new features, but old features didn't break. The new structure follows the modern standards of the JS community (ES Modules). It was inevitable for this change to happen; it would be detrimental for Meteor to follow the non-standard and not adapt to the change.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you want to take advantage of code splitting and dynamic importing, then yes, you will have to put some time into refactoring your application to do so. But that's not Meteor specific, it's just how life is.
I guess Meteor does so much out of the box, you might forget it can't (not yet, at least) write your app for you!
The main takeaway from this should be: your Meteor
1.0project from many moons ago will still run on Meteor1.8.1(the latest recommended release). There is no need to refactor anything. During the evolution from1.0to1.8.1Meteor has gained all kinds of great new features, fixes and improvements, but they are, at least to my knowledge, 99% non-breaking and/or optional. That's quite something.That sounds right. Sure, you obviously may need to update structure to use new features, but old features didn't break. The new structure follows the modern standards of the JS community (ES Modules). It was inevitable for this change to happen; it would be detrimental for Meteor to follow the non-standard and not adapt to the change.