
Research
Supply Chain Attack on Axios Pulls Malicious Dependency from npm
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.
@dbbs/next-cache-handler-core
Advanced tools
Support to control cache behaviour for NextJS applications.
@dbbs/next-cache-handler-core is designed to elevate the performance of Next.js applications by providing a robust caching solution that adapts to cookies, query parameters, and device types. This enables the delivery of content that is finely tuned to the context of each user, significantly improving load times and user experience.
Ensure you have Node.js version 12 or higher installed.
npm i @dbbs/next-cache-handler-core
# or
yarn add @dbbs/next-cache-handler-core
Create a cacheHandler.js in your project and configure as follows:
import { Cache, FileSystemCache } from '@dbbs/next-cache-handler-core'
Cache
.setCacheStrategy(new FileSystemCache())
.addCookies(['my-cookie-1','my-cookie-2'])
.addQueries(['my-query-1','my-query-2'])
.addDeviceSplit()
// Additional configuration...
export default Cache
Update your next.config.js to use the cache handler.
const nextConfig = {
cacheHandler: require.resolve('./cacheHandler.js')
}
export default nextConfig
Explore various caching strategies to find the best fit for your application's needs:
import { Cache, MemoryCache } from '@dbbs/next-cache-handler-core'
Cache.setCacheStrategy(new MemoryCache())
import { Cache, MemoryCache } from '@dbbs/next-cache-handler-core'
// extending size limitation to 1024MB.
Cache.addStrategy(new MemoryCache({ sizeLimit: 1024 }))
import { Cache, FileSystemCache } from '@dbbs/next-cache-handler-core'
Cache.setCacheStrategy(new FileSystemCache())
import { Cache } from '@dbbs/next-cache-handler-core'
import { RedisCache } from '@dbbs/next-cache-handler-redis'
// list of all accepted redis connection options.
const redisConnectionOpts = {
url: 'redis://localhost:5843',
...
}
Cache.setCacheStrategy(new RedisCache(redisConnectionOpts))
import { Cache } from '@dbbs/next-cache-handler-core'
import { S3Cache } from '@dbbs/next-cache-handler-s3'
Cache.setCacheStrategy(new S3Cache('cache-bucket-name'))
addCookiesCookie names what is going to be used to fragmentate cache based on browser cookies session.
Cache.addCookies(['my-cookie-to-split'])
addQueriesQuery names to fragmentate cache based on url query parameters.
Cache.addQueries(['my-query-to-split'])
addDeviceSplitEnables to fragmentate experience based on current User-Agent of the request.
Cache.addDeviceSplit()
setCacheStrategyApplies given strategy to cache page data.
Cache.setCacheStrategy(new MemoryCache())
addNoCacheRouteAdd route to ignore cache list. All routes added here would be excluded from caching and will always render again.
Cache.addNoCacheRoute('/home')
Leverage the built-in logger for monitoring cache operations or integrate your custom logger for advanced logging capabilities.
import { BaseLogger, Cache, FileSystemCache } from '@dbbs/next-cache-handler-core'
class MyCustomLogger implements BaseLogger {
constructor() {}
info(data) {
console.log(data)
}
error(data) {
console.error(data)
}
}
Cache.setCacheStrategy(new FileSystemCache).setLogger(new MyCustomLogger())
The next-cache-handler is open-source software licensed under the MIT License.
We value your feedback and contributions to the next-cache-handler. If you have any questions or suggestions or need support, here are several ways to get in touch with us:
General Inquiries and Support: For any general questions about the platform or if you need assistance, please visit our website DBB Software and use the contact form provided.
GitHub Issues: For specific issues, feature requests, or bugs related to the platform, please use the GitHub Issues page. This is the fastest way to directly communicate with our development team and track the resolution of your issue.
Community Discussion and Contributions: Join our community discussions on GitHub Discussions for broader topics, ideas exchange, and collaborative discussions.
Social Media: Follow us on our social media channels for the latest news, updates, and insights:
Email Contact: For more formal or detailed inquiries, feel free to reach out to us via email at in@dbbsoftware.com.
We're always here to help and are committed to ensuring you have the best experience with the next-cache-handler. Your input and participation drive the continuous improvement of our platform.
FAQs
Support to control cache behaviour for NextJS applications.
We found that @dbbs/next-cache-handler-core demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.

Research
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.

Security News
TeamPCP is partnering with ransomware group Vect to turn open source supply chain attacks on tools like Trivy and LiteLLM into large-scale ransomware operations.