Release 1.4.2.2 (and 1.4.2.3) #8044
Conversation
This solves a problem that sometimes occurs when new modules are added to an app but the cached Resolver object cannot find them because its statOrNull method is still using a previous instance of the corresponding ImportScanner. Related issues and comments: https://forums.meteor.com/t/meteor-not-detecting-new-files/31151 meteor-vue/vue-meteor#80 #7975 (comment) #8008
|
Very happy to see you guys adding new features to the accounts system and minimongo. |
Scaffold an official project structure Add --bare option to meteor create Notice scaffold options on meteor create add full skeleton add spaces remove shell-server package from skew-full + add description of new packages Add --bare option to meteor create Notice scaffold options on meteor create add full skeleton add spaces remove shell-server package from skew-full + add description of new packages improve PR resolve conflict Fix rebase fix static-assets readme Fix tipo Remove insecure and auto publish packages Remove useraccounts-configuration.js add tests fix PR
|
@benjamn Is it OK to add a compatibility breaking change ( |
|
@laosb You might be right… how much do those changes break backwards compatibility? We could always release those packages separately, later. |
|
Basically if users update, they need to add one more package to get config UI. |
…rd Method, which in turn prevents unnecessary audit-argument-checks warnings.
The options.transformFilename function is only supposed to transform target file names, not the names of source files to be copied. This behavior was broken by c5809a4 between Meteor 1.4.0.1 and 1.4.1. Thank goodness for `git bisect`! The biggest symptom of this mistake was that `meteor create --package` no longer created files based on the ~fs-name~.js and ~fs-name~-tests.js template files. This probably merits a 1.4.1.4 release in addition to 1.4.2.2.
If you call api.mainModule(path, where, { lazy: true }), that main
module will not be evaluated until other code imports it at runtime, and
won't even be bundled if no other code imports it.
Closes #6132.
Note that even an empty package needs to define Package[name] = {}, so
that other packages can tell at runtime whether it's installed.
Fixes #7927.
Thanks to @ptica for this suggestion: #8042 (comment)
|
@laosb After thinking about it over the weekend, I've decided to remove the |
This build includes another attempt to include python.exe reliably in the Windows dev bundle, thanks to https://github.com/winpython/winpython.
|
Please run |
|
I likely won't have a chance to test this tonight (your today). I'm not aware of any other issues which cannot wait for the next release. The only other 'trending' issue that I've seen in the last couple weeks is that Uglify's lack of harmony features (on the published branch) seems to be rearing its head more and more (#8020, #7994, #5517). I also haven't had an opportunity to verify that those would be fixed with the |
|
Yeah, last I checked the |
|
After taking a closer look at #8045, even though Meteor 1.4.2.2 is already final (but not yet "recommended"), I think it's worth immediately publishing a 1.4.2.3 release with @dburles' changes. Lots of folks are going to encounter those skeleton files before they know anything else about Meteor, so it seems really important for them to demonstrate good style and code structure. |
|
Good call on the move for 1.4.2.3. Also, if it's any assurance, I saw no issues with Meteor 1.4.2.2-rc.1 in my tests on my own apps. |
This is an improvement that I noticed while investigating the feasibility of fixing #8068.
|
Hi Ben, I used your suggested beta for the file not change issue. It works better. But I noticed meteor does not recognize small changes consistently. E.g. When I make a A HREF with too much quotes. I save, then meteor shows the error. I remove the extra quote but it does not update.
to
I saw the same thing yesterday when I had too much blaze }}}. {{template}}} to {{template}} |
|
mmm, could it be I press save too soon... and meteor is not yet checking my files? |
This comment has been minimized.
This comment has been minimized.
|
|
Minor follow-up release to Meteor 1.4.2.1.
In addition to what's currently on
devel, here are the issues I'm hoping to address with this release:Detection of newly added files:
Reify-related issues (possibly to be postponed to 1.4.3):