I second the request. My use case is this. I already have a bunch of fine-grained folders: folder “author” contains “author.html” and “author.js”, etc.
I don’t want to further clutter my space with adding one-file “client” and “server” subfolders. If my “author” folder contains “author.html”, “client.js” and “server.js” and maybe a couple of other files, that’s the granularity I’d feel most comfortable with.
In fact, I came to this forum looking for a way to hack Meteor to do just that.
This solution does not work like server/ and client/ folders, because server code will be sent to client. So if you have a lot of server code or your server code contains some secure information, then this method fails.
Yes, it would work, but also it will force you to manually register all files in your project which is not a pleasure task.
@imkost Yep! This way has some limitation) But I suppose it is better to manage every file in a project and manage dependecies and load order by the hand. I have found this realy clear for building separate UI (templates + styles) for web/cordova or adding new features by api.use/api.imply. Give it a try - it could save the time later