mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
c5f6c270b7
Should resolve #10233, reported by @klaussner. Previously, if a compiler plugin called inputFile.addJavaScript multiple times with different { path } strings, Meteor would allow importing all of those modules at once by importing the original source module identifier, by synthesizing a new source module containing a series of re-exports for each of the generated modules. Preserving this behavior is important for backwards compatibility, since some compiler plugins still generate files like "module.ext.js" given an input file named "module.ext", so Meteor tries to make those modules interchangeable/synonymous. However, if the compiler plugin explicitly calls inputFile.addJavaScript with the original source path, then it would be a mistake to modify the contents of that module, so Meteor will now leave the contents of that explicit source module unmodified, rather than using it as a catch-all way to import other generated modules.
modules
To run the tests, first install the npm dependencies, then run the app:
npm install
npm test # just does `meteor run`
then visit localhost:3000 in your browser.