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
Many changes #166
Many changes #166
Conversation
Thanks for this PR! I'll take a look through it when I have some time. |
Hey @jasrusable are you able to get this merged in? |
@jasrusable ? I wanted to use the project with these changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @dougg0k :) I took a quick look through the PR, for the most part I think it looks great! Thanks again.
Two main things though:
- I'd prefer to stick with vanilla
npm
for the sake of its ubiquity for now. - I'd prefer to use
date-fns
overdatejs
due to its simplicity.
Would you mind please implementing those changes?
I'll take a look at this test and see if I can spot why it might be flaky. |
|
What errors does npm give on installation? Can you share the error logs? |
Nevermind, it did while I was working on it. |
https://github.com/raineorshine/npm-check-updates Much better and easier to update libs while not having the bloat of dependabot and attempts of lib updates that goes to ESM only. You can just |
Great, then last few things:
|
May I ask why keep it compatible with older versions than 14 LTS? Because of older versions I had to downgrade Jest, which required to downgrade Typescript and now other libraries and now the need for It's prefered to keep oudated libs for the sake of old nodejs versions? @jasrusable |
package.json
Outdated
"dayjs": "1.11.5", | ||
"debug": "4.3.4", | ||
"ioredis": "5.2.3", | ||
"p-queue": "6.6.2", | ||
"p-timeout": "4.1.0", | ||
"rate-limiter-flexible": "2.3.12", | ||
"set-interval-async": "3.0.2", | ||
"uuid": "9.0.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think dependencies
in "library"-like packages should be fixed to exact versions. Could we still have carets here, please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't that the whole point of have proper versions and to keep compatibility? Caret may install a different version than what you see.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
caret are minor + patch. Maybe no breaking changes if every lib are following the semantics.
Can you re-run the CI? @jasrusable |
Now it's one incompability with Can I drop v12 from tests, too? Will you take a look at that failing test? @jasrusable |
I’ll take a look at the remaining failing tests. |
Cool, thanks. |
@dougg0k seems it's just a single test that fails intermittently. Can you try increasing the sleep time to see if that fixes the test? |
Yeah, that is the test I mentioned in the PR first msg, I already tried increasing before, didnt work. @jasrusable |
I mean, if passes and fails randomly with the same value, must be a bug somewhere. After trying multiple runs. I saw some random fails of.
It seems to be related to the same bug. Where it expect the task to be stalled but are not. |
I tried running where one time succeeded and one failed. Any idea what could cause it to behave like this? @jasrusable Seems like
I will leave the rest to you. |
Strange, I cannot reproduce this failing test locally at all now, with either combination of Node 14, 16 or 18, Redis 4 or 5. |
@dougg0k I'm going to merge this PR for now because I'm happy with the changes otherwise. I'll do a bit more debugging locally and on GitHub Actions regarding this failing test before making a new release. |
Hello!
A few days ago I looked at the project and got interested in it, seemed to be a better option than bee-queue. And I looked through the issues and made this PR.
But this PR contains more things than that.
npm
topnpm
which are very fast. and is the one I have been using in my projects. After trying to install packages using recentnpm
version, it that was complaining / giving errors.It could be worth upgrading to
ioredis
latest version, seems that is more stable but there are breaking changes. As for thep-
starting dependencies, it is in the latest version that is usable in non-ESM projects. While the rest are up-to-date.Edit: I upgraded ioredis to v5, only small breaking changes, mostly in the typing.
Edit2: There is a test that randomly fails. Been happening before I started the changes though. Sometimes I get consecutives test run all successful and sometimes consecutives 1 fail with that one below.
It's up to you to accept or not. All tests seem to be passing.
@jasrusable