github/meteor
1
1
Fork 0
mirror of https://github.com/meteor/meteor.git synced 2026-05-02 03:01:46 -04:00
Code Issues Packages Projects Releases Wiki Activity

Fix bad link

Browse Source
This commit is contained in:
skirunman
2016-04-07 00:11:38 -07:00
committed by Sashko Stubailo
parent 1f5ca3c151
commit f9a6e314bc
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/client/full-api/packages/modules.md
View File

@@ -164,7 +164,7 @@ A version of the `npm` command comes bundled with every Meteor installation, and
### File load order
Before Meteor 1.3, the order in which application files were evaluated was dictated by a set of rules described in the [Structuring Your Application](http://docs.meteor.com/#/full/structuringyourapp) section of the docs (see **File Load Order** subheading). These rules could become frustrating when one file depended on a variable defined by another file, particularly when the first file was evaluated after the second file.
Before Meteor 1.3, the order in which application files were evaluated was dictated by a set of rules described in the [Application Structure - Default file load order](http://guide.meteor.com/structure.html#load-order) section of the Meteor Guide. These rules could become frustrating when one file depended on a variable defined by another file, particularly when the first file was evaluated after the second file.
Thanks to modules, any load-order dependency you might imagine can be resolved by adding an `import` statement. So if `a.js` loads before `b.js` because of their file names, but `a.js` needs something defined by `b.js`, then `a.js` can simply `import` that value from `b.js`: