AFAIK Meteor is not supporting this exactly in that way. So you are left with two workarounds.
One would be writing a own extension which helps you in that regard or finding one which already exists.
And the other would be putting your special resources somewhere in the
/yourMeteorApp/public folder which is excluded from the merge process (see http://docs.meteor.com/#/full/structuringyourapp). And now you could write some template specific logic to load and evaluate JS and CSS resources from there when your template is accessed. Resources in
public are available directly on root level - so
public/js/my.js would be available under
This answer is quite old and in modern Meteor apps you should make use of the import logic (and the
imports folder) which didn't exist in that way when I originally answered this: https://guide.meteor.com/structure.html#intro-to-import-export
This should be the best way to handle any dynamic JS requirements and strucutre an app by far nowadays.