Ideal project structure for a post-imports Meteor world?

help
1

With the /imports folder no longer having special significance for Meteor-based apps, I’m curious how people are organizing their project structures? I’ve seen some projects just move everything to the root folder, but that seems to get messy. Others are just replacing imports with /lib or /app or /src, but those seem to have different significance based on the developer’s background.

Is there a recommended best practice for file structure in the post-1.7 Meteor world?

2 Likes
2

I still do it the old way so I have no big cognitive workload when switching between newer and older projects. However I would also like to get some inspiration on this topic.

3 Likes
3

If “imports” doesn’t become copyrighted, forbidden by law or immoral I’ll stick with it. For the sake of change I am thinking to misspell it.

3 Likes