• Added worker queues
• Jobs - WorkerService.addJob
• Cron Jobs - WorkerService.addCronJob
• EmailService now has option to add email to queue EmailService.sendEmail(emailCategory, { addToQueue: true })

Bumps ejs from 3.1.6 to 3.1.7.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Easy to use javascript APIs to send transactional notifications to users via Email

• [x] Functions to sendEmail(notificationCategory, contextData, { to, text, from })
• [x] Testing using ethereal
• [x] Templates
• [x] Managing notification categories with respective templates
• [x] Email branding - logo/color, header, footer, social links

How to reproduce - After login, head over to /user/profile, check the server logs, you'll see following error

GET /user/profile 302 17.288 ms - 148
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at new NodeError (node:internal/errors:371:5)
    at ServerResponse.setHeader (node:_http_outgoing:576:11)
    at ServerResponse.header (/home/johndoe/Projects/supertokens/example/saas-express-starter-kit/node_modules/express/lib/response.js:767:10)
    at ServerResponse.send (/home/johndoe/Projects/supertokens/example/saas-express-starter-kit/node_modules/express/lib/response.js:170:12)
    at done (/home/johndoe/Projects/supertokens/example/saas-express-starter-kit/node_modules/express/lib/response.js:1004:10)
    at tryHandleCache (/home/johndoe/Projects/supertokens/example/saas-express-starter-kit/node_modules/ejs/lib/ejs.js:280:5)
    at View.exports.renderFile [as engine] (/home/johndoe/Projects/supertokens/example/saas-express-starter-kit/node_modules/ejs/lib/ejs.js:491:10)
    at View.render (/home/johndoe/Projects/supertokens/example/saas-express-starter-kit/node_modules/express/lib/view.js:135:8)
    at tryRender (/home/johndoe/Projects/supertokens/example/saas-express-starter-kit/node_modules/express/lib/application.js:640:10)
    at Function.render (/home/johndoe/Projects/supertokens/example/saas-express-starter-kit/node_modules/express/lib/application.js:592:3)

There are two improvements that can further make the config management robust

• [ ] Use one config file only (remove dev vs prod config, just one file instead)
• [ ] A mechanism that ensures no config is missing from sample config (can use dotenv-safe for this)

Goal

Boilerplate code to speed up development of a new SaaS app

Principles

Broadly, we can follow these principles to make the project useful with a good developer experience

1. Must have some Complete Features: These features are ready to use (these features do not expect much different implementations in different use cases e.g. auth)
2. Must have some Abstract APIs: These APIs(functions/services) help in building some of the most frequently used features in SaaS (where implementation vary a lot based on the use case e.g. email service, user roles, etc.)
3. Changes should be easy
   • Changes in Complete Features should be driven by configuration changes (e.g. replacing email/password login with passwordless login)
   • Changes in Abstract APIs should be driven by changing or extending the code
   • Abstract APIs should be documented
   • No styling opinion, a frontend without styling
   • Code Smells - If a dev needs to remove code or change the code structure in order to build their use case
   • Keep it lean

Agree? Give it a thumbs up :+1: Have feedback for goal/principles? Comment your thoughts

For now, we use no CSS at all, but real world application wouldn't do that. We did that to make sure we do not make any opinions on the design because we expect that the end user is going to change the design to match their brand and choice anyway. So changing an already opinionated design system will be harder than to start from element without any design at all. But how can we even make this work easier?

Answer: Provide a sample css theme that can be dropped in public/stylesheets folder and that should automatically change the design for the whole app. We still adhere to the rule that we don't add any opinion about the design elsewhere in the code (i.e. no element styles in html inline, no reference to any other external css.

Make it easier for people to add their choice of email transporter from following

• [ ] Amazon SES
• [ ] Mailgun
• [ ] Mailchimp
• [ ] Postmark
• [ ] SendGrid
• [ ] SparkPost

Resource - https://nodemailer.com/transports/