Deprecate delighted package - Delighted sunset June 30, 2026

[jflores-q]

Summary

Delighted is being sunset on June 30, 2026. This is the final release of the delighted Node.js package (v2.2.0), marking it as deprecated.

For more information, visit the Delighted Sunset FAQ.

Changes

• delighted.js: Added console.warn() deprecation notice at the top of the entry point. Every user who require('delighted') will see the warning in their server logs.
• lib/Delighted.js: Bumped VERSION from '2.1.0' to '2.2.0'.
• package.json: Bumped version from "2.1.0" to "2.2.0".
• README.md: Added deprecation banner at the top. This is the first thing users see on the npm package page.
• CHANGELOG.md: Added 2.2.0 deprecation entry.

What users will see

On npm install delighted: npm deprecation warning (already applied via npm deprecate).

On require('delighted'):

[delighted] DEPRECATION NOTICE: Delighted is being sunset on June 30, 2026.
This package is deprecated and will no longer be maintained or receive updates.
For more information, visit the Delighted Sunset FAQ:
https://help.delighted.com/article/840-delighted-sunset-faq

Pre-merge validation (all passed)

Check	Result
node -e "require('./delighted')('test')"	console.warn deprecation message printed to stderr
npm deprecate (retroactive)	Already applied to all versions

After merging

1. Tag the release as v2.2.0
2. Publish to npm: npm publish --tag latest
3. Archive this GitHub repository

Local validation steps

1. Test runtime warning (from repo root)

node -e "var d = require('./delighted')('test')"

You should see the [delighted] DEPRECATION NOTICE message on stderr.

2. Verify npm deprecation is already active

npm view delighted deprecated

3. Verify version constants match

node -e "console.log(require('./package.json').version)"
# Expected: 2.2.0