@nilsdannemann One thing to note here is that the import keyword won’t work within a Meteor.isServer block. You will have to use a regular node require in that circumstance. If you’ve structured your code in such a way that you don’t have Meteor.isServer blocks then you don’t need to worry about it. Thought I should mention it just in case your app is breaking and you can’t figure out why

@nilsdannemann No you can totally put import in the server folder. I’m referring to code that lives in the lib folder (where many people put Meteor methods and other universal code). Because code in the lib folder runs on both the client and server it is sometimes necessary to specify that a particular bit of code runs only on the server with Meteor.isServer. Here are some examples of what will and will not work:

Won’t work

if (Meteor.isServer) {
import moment from 'moment';
// Use moment
}

Will work

import moment from 'moment';
if (Meteor.isServer) {
// Use moment
}

Will work

if (Meteor.isServer) {
let moment = require('moment')
// Use moment
}

These examples just illustrate that if you want to pull in a library within a Meteor.isServer block you need to use the require statement. Otherwise you can use import at the top of the file.

Everything worked (although the newest webshot version seems to have problems with bootstrap css).
I’ve cloned your repo, made a new branch, added an updated version in a final_updated folder and tried to send a pull request. Unfortunately I got an error: