You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
In packages such as https://github.com/mizzao/meteor-build-fetcher and https://github.com/Nemo64/meteor-translator, .json. and .yml files are used to generate javascript respectively, and should be able to decide if a file is going to be added bare or not during the build process. Whether the parent file is bare or not should have no bearing on this, except as a possible input to be provided.
Packages that try to add bare files in the build process just get ignored now.
I don't think this change was thought through particularly, as
This was changed in commit cf68cd7
In packages such as https://github.com/mizzao/meteor-build-fetcher and https://github.com/Nemo64/meteor-translator,
.json
. and.yml
files are used to generate javascript respectively, and should be able to decide if a file is going to be added bare or not during the build process. Whether the parent file is bare or not should have no bearing on this, except as a possible input to be provided.Packages that try to add bare files in the build process just get ignored now.
I don't think this change was thought through particularly, as
meteor/tools/compiler.js
Line 780 in abbda82
options.bare
whilefileOptions.bare
is used later on.@stubailo, your thoughts please?
The text was updated successfully, but these errors were encountered: