René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Setting undefined as value, getting null back (version 5.1.2)","articleBody":"I'm using node-cache 5.1.2 and this is the little example code that I have:\n\n```ts\nimport NodeCache from 'node-cache'\n\nconst cache = new NodeCache({\n  stdTTL: 900,\n  checkperiod: 900 / 5,\n  useClones: false,\n})\n\ncache.set('hello', undefined)\nconst restored = cache.get('hello') // incorrectly returns null\n```\n\nI found this [already closed issue](https://github.com/node-cache/node-cache/issues/264), don't know whether it is caused by same thing, but the issue still definitely persists.\n\nIf anyone finds this issue my current workaround is to wrap every data that I store into an object, like this:\n\n```ts\ncache.set('workaround', { value: undefined })\nconst restored = cache.get('workaround').value // correctly returns undefined\n```","author":{"url":"https://github.com/meszaros-lajos-gyorgy","@type":"Person","name":"meszaros-lajos-gyorgy"},"datePublished":"2025-11-20T21:59:43.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/330/node-cache/issues/330"}