VS Code + Meteor and help in migrating away from globals

help
21

Now, if only we had a way of importing all template inclusions automatically… I suppose you didn’t get that far with your improvements on ImportJS? :face_with_raised_eyebrow:

<template name="parent">
  {{> child ''}}
</template>

import './child'; // <---- THIS ONE
Template.parent.onCreated(function () {
   ...
});
22

Yeah, those we did by hand, whenever we had to touch one of the templates.
It took another year before we could turn off eager loading of every blaze template

23

Did you ever get ImportJS to work inside packages themselves? The first requirement seems to be an existing package.json file, which the packages don’t have normally have.

For example, this is my file structure and ImportJS ain’t playing nice:

.
..
meteor-packages/
  package1/
  package2/
  package3/
app1/
  packages/
     package1/ (symlink)
app2/
  packages/
     package2/ (symlink)
app3/
  packages/
     package1/ (symlink)
     package2/ (symlink)
     package3/ (symlink)
24

For code in packages, it can only identify dependencies of the main app, not the ones declared by app.use in package.js.

So when I was converting, I just added every package to the main app in question.

Not sure if symlinks mess it up either, we use git submodules