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

fix: migrating to @cacheable/node-cache as it is maintained #1074

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jaredwray
Copy link

Looking to use this and node-cache is not being maintained so I built a new one under my current caching project. This is fully maintained with monthly updates.

@whiskeysockets-bot
Copy link
Contributor

Thanks for your contribution.

The next step is to wait for review and approval to merge it to main repository

The community can help reacting with a thumb up (:thumbsup:) for approval and rocket (:rocket:) for who has tested it.

To test this PR you can run the following command below:

# NPM
npm install @whiskeysockets/baileys@jaredwray/Baileys#fix-migrating-to-@cacheable/node-cache-as-it-is-maintained
# YARN v2
yarn add @whiskeysockets/baileys@jaredwray/Baileys#fix-migrating-to-@cacheable/node-cache-as-it-is-maintained

@Skidy89
Copy link

Skidy89 commented Oct 4, 2024

baileys is written in commonjs (i think)

@jaredwray
Copy link
Author

Yep. This should still work

@jaredwray
Copy link
Author

@Skidy89 or @purpshell - can you let me know if this pull request is going to be accepted?

@purpshell
Copy link
Collaborator

@Skidy89 or @purpshell - can you let me know if this pull request is going to be accepted?

I am looking into it, the whole caching scene in Baileys might change dramatically after the universal storage changes. We'll def. look into this package though, the replacement makes sense. Thanks for maintaining node-cache under your project.

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 this pull request may close these issues.

4 participants