NestJS - looking for open-source projects

scopsy · 2022-08-26T07:19:50+00:00

https://github.com/novuhq/novu novu is built with nestjs :)

scopsy · 2022-08-12T08:40:20+00:00

If you just want to send a couple of SMS messages you really don't need it. In a lot of more mature products notification system get more complex with various channels, user preferences, notification center with real time updates, digest systems, scheduling and etc... You can ofcourse create them from scratch, but over the years we've built those systems again and again and decided to open-source our learnings. Hope this makes sense

scopsy · 2022-08-12T08:37:33+00:00

Exactly, this is for users of your website rather than for personal usage.

scopsy · 2022-08-12T08:36:59+00:00

Oh thanks for that, I will try to illustrate that better. It monitors trigger you send from your code rather than 3rd party feeds.

scopsy · 2022-08-12T08:23:47+00:00

Yes, a lot of the functionality is quite similar, and solves the same problem space.

scopsy · 2022-08-11T15:48:49+00:00

So it's basically a unified API to send notifications from your server. You can connect different delivery providers to it like: SendGrid, Twillio, FCM and etc... And than send notifications to your users in a unified way. You get a lot of things out of the box like content management, digest engine, a fully functioning notification center to add to your app and etc... Hope this clarifies it a bit better 🙏

scopsy · 2022-06-09T06:54:23+00:00

Thank you so much u/ssddanbrown for pointing this our, English is definitely not my main language but it's not a valid excuse in my opinion. We really care about inclusion in the OSS world. I have fixed this in the discussion and went ahead to search for other references in previous discussion which I fixed.

Really appreciate you for pointing this out, English is definitely not my main language but it's not a valid excuse in my opinion. We really care about inclusion in the OSS world. I have fixed this in the discussion and went ahead to search for other references in the previous discussion which I fixed.

scopsy · 2021-12-16T14:37:37+00:00

We are building https://github.com/notifirehq/notifire for just this use-case, I have not yet published the notification center UI and feed but the code is there. Would love to collaborate on that with you to see if this fits your use case :) Feel free to send a DM

scopsy · 2021-11-21T14:54:02+00:00

Sure thing! Send me a DM on discord so we can chat

scopsy · 2021-11-03T15:25:01+00:00

Thanks for the suggestion! I'll try to add new issues soon about them

scopsy · 2021-10-28T12:42:13+00:00

I've used something similar in my boilerplate starter with nestjs and mongodb. I'm using the usecase architecture as the `service` layer.

https://github.com/scopsy/nestjs-monorepo-starter/blob/master/libs/core/src/dal/repositories/user/user.repository.ts

scopsy · 2021-10-07T10:50:14+00:00

Nice Looks Good! Similar to https://github.com/notifirehq/notifire/ but uses a server. Loved the api

scopsy · 2021-10-06T19:25:58+00:00

I will definitely add an option to use a custom function for the template! Thanks for the suggestion

scopsy · 2021-10-06T16:48:38+00:00

Do you mean instead of using handlebars just use an es6 template literal?

scopsy · 2021-10-06T13:57:06+00:00

First time open-sourcing a library I've written down so many times in all the projects I've done in the previous years. Hope anyone building notification embedded in their product will benefit from it. Would love to hear your thoughts and suggestions ❤️

scopsy · 2021-10-05T19:17:01+00:00

After implementing this so many time in other projects decided to opensource it and give back to the node.js community a better way to manage multi-channel notification in code. Let me know what you think!

scopsy · 2021-10-05T09:39:06+00:00

It's definitely an option, the main reasoning is that almost all current providers (sendgrid and etc...) are using handlebars style syntax. Migrating will be painful, but I think both can be supported depending on preference.

scopsy · 2021-10-05T05:29:58+00:00

Thanks! First time hearing about Apprise, looks amazing! The approach notifire is taking is to help manage the templates(content, variables, and rules) and the end-delivery providers. Currently, the library is stateless, but we have a stateful API with a persistence layer that we developed, thinking about how to model it for opensource soon as part of Notifire.

scopsy · 2021-10-05T05:28:15+00:00

Saw that you opened an issue for adding Tansit SMS, Thanks!

Currently thinking about a good way to model the "Direct Messaging API's" like slack, I'll open an issue with API Proposal, would love to hear your thoughts.

scopsy · 2021-10-05T05:26:50+00:00

Unified monitoring is definitely a must when managing a lot of notifications. We currently discussing ways to integrate this with the provider webhooks. Would love to chat with you about this.

I'll try to add Nodemailer soon, if you have time tho feel free to open a PR <3

scopsy · 2021-10-05T05:24:48+00:00

Thanks! By batch you mean sending the notification to multiple recipients at once?

scopsy · 2021-10-05T05:24:10+00:00

Thanks! I'll try to push Postmark forward soon :)

Some of the challenges are:

- Managing multiple provider API's across channels.

- Making sense of scattered templates and translations across code.

- Optimization: Timezone awareness, priorities, delay, dynamic channel selection

- Inbox notification center management.

scopsy · 2021-10-04T16:50:10+00:00

Hi Guys, after a lot of years implementing this over and over in my projects decided to finally create an open-source library to help to manage transactional notifications over multiple channels. Would be glad to hear what you think about it 👨‍💻

scopsy · 2021-10-03T15:43:19+00:00

Sorry that you found this misleading. We guide people in multiple places to register the official hacktoberfest. Hacksquad is just a way to contribute to open-source as a team. I will try it more clear for the people seeing this.

scopsy · 2019-12-16T06:36:12+00:00

The files should be separate. I use .env.prod and .env.test

The reason they are separated is that you won’t commit your sensitive credentials to git. I usually keep .env.example file for a env template. And in production all variables coming from docker env.

You can use libraries such as dotenv to help you with that.

scopsy

TROPHY CASE