Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bring agendaTS into agenda main repo #1502

Open
2 of 4 tasks
simllll opened this issue Nov 8, 2022 · 18 comments · Fixed by #1503
Open
2 of 4 tasks

bring agendaTS into agenda main repo #1502

simllll opened this issue Nov 8, 2022 · 18 comments · Fixed by #1503

Comments

@simllll
Copy link
Contributor

simllll commented Nov 8, 2022

As discussed and suggested here #1082 the idea is to bring agendaTS as new major version of agenda main.

Checklist (WIP):

  • try to create a PR that is based on the current agenda master, and try to keep as many commits from the agendaTS to have a change history. in case of merge conflicts, keep the agendaTS code.
  • rename everything back to agenda
  • improve docs of new features
  • write down list of breaking changes and transition guide

New features in agendaTS:

List of currently known breaking changes:

feel free to add comments, ideas and other things you come up with :)

@harisvsulaiman
Copy link
Member

What about tests?

@harisvsulaiman
Copy link
Member

@simllll I hope this will be a starting point.

@harisvsulaiman harisvsulaiman linked a pull request Nov 8, 2022 that will close this issue
@simllll simllll reopened this Dec 2, 2022
@harisvsulaiman harisvsulaiman pinned this issue Dec 2, 2022
@harisvsulaiman
Copy link
Member

@simllll Is there any update on this issue?

@simllll
Copy link
Contributor Author

simllll commented Feb 20, 2023

Sorry for still not working on it, I have it still in my list, but couldn't really find time yet. Hopefully within the next few weeks though!

@harisvsulaiman
Copy link
Member

@simllll Is this on the agenda ? (Pun intended)

@simllll
Copy link
Contributor Author

simllll commented May 13, 2023

It's still on my list, but unfortunately didn't find time yet... Maybe I can start working on it next weekend, to get things rolling... 🤞

@harisvsulaiman
Copy link
Member

@simllll let me know if you need anything. I will try to find time to help out if possible

@sebamarynissen
Copy link

Hi there,

Would it be possible to create a v5 branch based on 8f46df0? I've added support for mongodb@5, but it's based on the code of v5.0.0 that's on npm, and since #1503 it doesn't make sense to file a PR against the master branch - see #1547.

I think it would be nice to add support for mongodb@5 in a semver minor v5.1.0 without waiting for the next release with agendaTS merged into the repo.

@harisvsulaiman
Copy link
Member

@simllll Is there any update on this?

@GimpMaster
Copy link
Contributor

I'm curious on where I should get agenda as well. Looks like npmjs is showing version 5.0.0 only, but this repo shows change logs into the 6.X @simllll

@koresar
Copy link
Contributor

koresar commented Feb 23, 2024

@GimpMaster the 6.x development halted unfortunately.

@GimpMaster
Copy link
Contributor

@koresar - is the 5.X considered stable? I’m still back on 3.X and was just looking to upgrade.

@koresar
Copy link
Contributor

koresar commented Feb 23, 2024

I do not know which is more stable. Sorry.

@sebamarynissen
Copy link

@GimpMaster 5.x is stable, but it doesn't work with mongodb@6 due to a few breaking changes in the mongodb package.

I've published my own fork @whisthub/agenda on npm, which is compatible with mongodb 4, 5 and 6 (beware mongodb is a peer dependency now). I've been using this in production for about 3 weeks now without any issues.

@GimpMaster
Copy link
Contributor

Thank you

@tomups
Copy link

tomups commented Mar 12, 2024

@sebamarynissen thanks for that, got excited for a moment but because your fork is ESM only, it doesn't work with NestJS :(

Hopefully NestJS will move to ESM one of these days...

@sebamarynissen
Copy link

@tomups Is it an option for you to use dynamic import? As most of agenda is async anyway, this could be an option in cjs projects:

const { default: agenda } = await import('@whisthub/agenda');
await agenda.start();

// Instead of
const agenda = require('@whisthub/agenda');
await agenda.start();

@tomups
Copy link

tomups commented Mar 14, 2024

@sebamarynissen I don't use agenda directly in NestJS but via https://github.com/jongolden/agenda-nest which makes it work in a more NestJS way. So I don't think using dynamic import in that way would work. Maybe forking agenda-nest and trying it...

But with dynamic import we lose TypeScript types :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants