@creowis/intl-date-utils 1.0.0

package/.all-contributorsrc

@@ -0,0 +1,35 @@
+{
+  "files": [
+    "README.md"
+  ],
+  "imageSize": 100,
+  "commit": false,
+  "commitType": "docs",
+  "commitConvention": "angular",
+  "contributors": [
+    {
+      "login": "atapas",
+      "name": "Tapas Adhikary",
+      "avatar_url": "https://avatars.githubusercontent.com/u/3633137?v=4",
+      "profile": "https://tapasadhikary.com",
+      "contributions": [
+        "code"
+      ]
+    },
+    {
+      "login": "ATechAjay",
+      "name": "Ajay Yadav",
+      "avatar_url": "https://avatars.githubusercontent.com/u/76649353?v=4",
+      "profile": "https://github.com/ATechAjay",
+      "contributions": [
+        "code"
+      ]
+    }
+  ],
+  "contributorsPerLine": 7,
+  "skipCi": true,
+  "repoType": "github",
+  "repoHost": "https://github.com",
+  "projectName": "intl-date-utils",
+  "projectOwner": "CreoWis"
+}

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+hello@creowis.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

package/CONTRIBUTING.md

@@ -0,0 +1,198 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via [issue](https://github.com/CreoWis/next-js-launchpad/issues),
+[email](mailto:hello@creowis.com), or any other method with the owners of this repository before making a change.
+
+Please note we have a [Code of Conduct](https://github.com/CreoWis/next-js-launchpad/blob/main/CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+
+- [Pull Request Process](#prp)
+- [Code of Conduct](#coc)
+- [Commit Message Format](#commit)
+
+## <a name="prp"></a> Pull Request Process
+
+1. Ensure any install or build dependencies are removed before the end of the layer when doing a
+   build.
+2. Update the README.md with details of changes to the interface, this includes new environment
+   variables, exposed ports, useful file locations and container parameters.
+3. Increase the version numbers in any examples files and the README.md to the new version that this
+   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
+   do not have permission to do that, you may request the second reviewer to merge it for you.
+
+## <a name="coc"></a> Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [hello@creowis.com](mailto:hello@creowis.com). All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/
+
+## <a name="commit"></a> Commit Message Format
+
+We have very precise rules over how our Git commit messages must be formatted.
+This format leads to **easier to read commit history**.
+
+Each commit message consists of a **header**, a **body**, and a **footer**.
+
+```
+<header>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+The `header` is mandatory and must conform to the [Commit Message Header](#commit-header) format.
+
+The `body` is mandatory for all commits except for those of type "docs".
+When the body is present it must be at least 20 characters long and must conform to the [Commit Message Body](#commit-body) format.
+
+The `footer` is optional. The [Commit Message Footer](#commit-footer) format describes what the footer is used for and the structure it must have.
+
+#### <a name="commit-header"></a>Commit Message Header
+
+```
+<type>(<scope>): <short summary>
+  │       │             │
+  │       │             └─⫸ Summary in present tense. Not capitalized. No period at the end.
+  │       │
+  │       └─⫸ Commit Scope: common|plays (2048, analog-clock, basic-calculator, etc.)|infra|etc.
+  │
+  └─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test
+```
+
+The `<type>` and `<summary>` fields are mandatory, the `(<scope>)` field is optional.
+
+##### Type
+
+Must be one of the following:
+
+- **build**: changes that affect the build system or external dependencies
+- **ci**: changes to our CI configuration files and script
+- **docs**: documentation only changes
+- **feat**: new feature
+- **fix**: bug fix
+- **perf**: code change that improves performance
+- **refactor**: code change that neither fixes a bug nor adds a feature
+- **test**: add missing tests or correcting existing tests
+
+##### Summary
+
+Use the summary field to provide a succinct description of the change:
+
+- use the imperative, present tense: "change" not "changed" nor "changes"
+- don't capitalize the first letter
+- no dot (.) at the end
+
+#### <a name="commit-body"></a>Commit Message Body
+
+Just as in the summary, use the imperative, present tense: "fix" not "fixed" nor "fixes".
+
+Explain the motivation for the change in the commit message body. This commit message should explain _why_ you are making the change.
+You can include a comparison of the previous behavior with the new behavior in order to illustrate the impact of the change.
+
+#### <a name="commit-footer"></a>Commit Message Footer
+
+The footer can contain information about breaking changes and deprecations and is also the place to reference GitHub issues, Jira tickets, and other PRs that this commit closes or is related to.
+For example:
+
+```
+BREAKING CHANGE: <breaking change summary>
+<BLANK LINE>
+<breaking change description + migration instructions>
+<BLANK LINE>
+<BLANK LINE>
+Fixes #<issue number>
+```
+
+or
+
+```
+DEPRECATED: <what is deprecated>
+<BLANK LINE>
+<deprecation description + recommended update path>
+<BLANK LINE>
+<BLANK LINE>
+Closes #<pr number>
+```
+
+Breaking Change section should start with the phrase "BREAKING CHANGE: " followed by a summary of the breaking change, a blank line, and a detailed description of the breaking change that also includes migration instructions.
+
+Similarly, a Deprecation section should start with "DEPRECATED: " followed by a short description of what is deprecated, a blank line, and a detailed description of the deprecation that also mentions the recommended update path.
+
+### Revert commits
+
+If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
+
+The content of the commit message body should contain:
+
+- information about the SHA of the commit being reverted in the following format: `This reverts commit <SHA>`,
+- a clear description of the reason for reverting the commit message.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 CreoWis
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,169 @@
+
+<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
+[![All Contributors](https://img.shields.io/badge/all_contributors-2-orange.svg?style=flat-square)](#contributors-)
+<!-- ALL-CONTRIBUTORS-BADGE:END -->
+# intl-date-utils
+
+Lightweight date utilities powered by the modern JavaScript Intl API.
+
+Features:
+
+- Zero dependencies
+- Intl-based formatting
+- Timezone aware
+- Relative time utilities
+- Small bundle size
+- Works in Node.js and modern browsers
+- Types enabled to work with TypeScript Projects
+
+## Installation
+Using NPM
+
+```bash
+npm install intl-date-utils
+```
+
+Using Yarn
+
+```bash
+yarn add intl-date-utils
+```
+
+Using Pnpm
+
+```bash
+pnpm install intl-date-utils
+```
+
+
+## Usage
+
+```js
+import { formatDate, timeAgo } from 'intl-date-utils'
+
+formatDate(new Date())
+timeAgo(new Date(Date.now() - 86400000))
+```
+
+## Available Methods
+
+| Method | Description | Example |
+|------|-------------|--------|
+| `formatDate(date, locale?, style?)` | Formats a date using locale-aware Intl date styles (`full`, `long`, `medium`, `short`). | `formatDate(new Date(), "en-US", "long")` |
+| `formatTime(date, locale?, style?)` | Formats only the time portion of a date using Intl time styles. | `formatTime(new Date(), "en-US")` |
+| `formatDateTime(date, locale?, options?)` | Formats date and time together with optional timezone support. | `formatDateTime(new Date(), "en-US", { timeZone: "Asia/Tokyo" })` |
+| `formatInTimezone(date, timeZone, locale?)` | Formats a date in a specific timezone regardless of system timezone. | `formatInTimezone(new Date(), "Asia/Tokyo")` |
+| `toLocaleDateISO(date, timeZone?)` | Returns a timezone-aware ISO calendar date string (`YYYY-MM-DD`). Useful for comparing dates across timezones. | `toLocaleDateISO(new Date(), "UTC")` |
+| `timeAgo(date, locale?)` | Returns human-readable relative time like "3 days ago" or "in 2 hours". | `timeAgo(new Date(Date.now() - 86400000))` |
+| `getMonthNames(locale?, style?)` | Returns an array of localized month names. | `getMonthNames("en-US")` |
+| `getDayNames(locale?, style?, startDay?)` | Returns localized weekday names with optional start day (0 = Sunday, 1 = Monday). | `getDayNames("en-US", "long", 1)` |
+| `formatRange(start, end, locale?, style?)` | Formats a date range using Intl range formatting. | `formatRange(new Date("2026-03-10"), new Date("2026-03-15"))` |
+| `isToday(date)` | Returns `true` if the provided date is today. | `isToday(new Date())` |
+| `isYesterday(date)` | Returns `true` if the date is yesterday. | `isYesterday(new Date(Date.now() - 86400000))` |
+| `isTomorrow(date)` | Returns `true` if the date is tomorrow. | `isTomorrow(addDays(new Date(), 1))` |
+| `startOfDay(date)` | Returns a new Date representing the start of the day (00:00:00). | `startOfDay(new Date())` |
+| `endOfDay(date)` | Returns a new Date representing the end of the day (23:59:59.999). | `endOfDay(new Date())` |
+| `addDays(date, amount)` | Adds or subtracts days from a date. | `addDays(new Date(), 5)` |
+| `addMonths(date, amount)` | Adds or subtracts months from a date. | `addMonths(new Date(), 2)` |
+| `differenceInDays(a, b)` | Returns the number of calendar days between two dates. | `differenceInDays(new Date("2026-03-15"), new Date("2026-03-10"))` |
+| `parseISO(value)` | Parses an ISO date string and returns a Date object with validation. | `parseISO("2026-03-15")` |
+| `formatSmartDate(date, locale?)` | Smart UI formatting (Today, Yesterday, relative time, or formatted date). | `formatSmartDate(new Date())` |
+
+## Development
+
+Install dependencies
+
+```bash
+npm install
+```
+
+Run tests
+
+```bash
+npm test
+```
+
+Build library
+
+```bash
+npm run build
+```
+
+## Test Package Locally
+
+Create npm tarball
+
+```bash
+npm pack
+```
+
+This generates:
+
+```bash
+intl-date-utils-1.0.0.tgz
+```
+
+You can test install locally:
+
+```bash
+npm install ./intl-date-utils-1.0.0.tgz
+```
+
+## Publish to npm
+
+Login
+
+```bash
+npm login
+```
+
+Publish
+
+```bash
+npm publish --access public
+```
+
+## License
+
+[MIT](./LICENSE)
+
+## 🤝 Contributing
+
+Contributions are always welcome!
+
+See [CONTRIBUTING.md](https://github.com/CreoWis/intl-date-utils/blob/main/CONTRIBUTING.md) for ways to get started.
+
+Please adhere to this project's [code of conduct](https://github.com/CreoWis/intl-date-utils/blob/main/CODE_OF_CONDUCT.md).
+
+## 🙏 Support Us
+
+This is an OSS project maintained by [CreoWis](https://www.creowis.com/). We need all the support we can get. Please give this project a ⭐️ to encourage and show that you liked it.
+
+If you found the project helpful, consider supporting us with a ☕
+
+<a href="https://www.buymeacoffee.com/creowis">
+    <img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" height="50px">
+</a>
+
+## Contributors ✨
+
+Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
+
+<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
+<!-- prettier-ignore-start -->
+<!-- markdownlint-disable -->
+<table>
+  <tbody>
+    <tr>
+      <td align="center" valign="top" width="14.28%"><a href="https://tapasadhikary.com"><img src="https://avatars.githubusercontent.com/u/3633137?v=4?s=100" width="100px;" alt="Tapas Adhikary"/><br /><sub><b>Tapas Adhikary</b></sub></a><br /><a href="https://github.com/CreoWis/intl-date-utils/commits?author=atapas" title="Code">💻</a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/ATechAjay"><img src="https://avatars.githubusercontent.com/u/76649353?v=4?s=100" width="100px;" alt="Ajay Yadav"/><br /><sub><b>Ajay Yadav</b></sub></a><br /><a href="https://github.com/CreoWis/intl-date-utils/commits?author=ATechAjay" title="Code">💻</a></td>
+    </tr>
+  </tbody>
+</table>
+
+<!-- markdownlint-restore -->
+<!-- prettier-ignore-end -->
+
+<!-- ALL-CONTRIBUTORS-LIST:END -->
+
+This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!

package/SECURITY.md

@@ -0,0 +1,21 @@
+# Security Policy
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 5.1.x   | :white_check_mark: |
+| 5.0.x   | :x:                |
+| 4.0.x   | :white_check_mark: |
+| < 4.0   | :x:                |
+
+## Reporting a Vulnerability
+
+Use this section to tell people how to report a vulnerability.
+
+Tell them where to go, how often they can expect to get an update on a
+reported vulnerability, what to expect if the vulnerability is accepted or
+declined, etc.

package/build.js

@@ -0,0 +1,19 @@
+
+import { build } from 'esbuild'
+
+await build({
+  entryPoints: ['src/dateUtils.js'],
+  outfile: 'dist/dateUtils.js',
+  format: 'esm',
+  platform: 'neutral',
+})
+
+await build({
+  entryPoints: ['src/dateUtils.js'],
+  outfile: 'dist/dateUtils.min.js',
+  format: 'esm',
+  minify: true,
+  platform: 'neutral',
+})
+
+console.log('Build complete')

package/package.json

@@ -0,0 +1,31 @@
+{
+  "name": "@creowis/intl-date-utils",
+  "version": "1.0.0",
+  "description": "Lightweight date utilities powered by the JavaScript Intl API",
+  "type": "module",
+  "main": "./dist/dateUtils.js",
+  "exports": {
+    ".": "./dist/dateUtils.js"
+  },
+  "scripts": {
+    "build": "node build.js",
+    "test": "node --test",
+    "prepare": "npm run build"
+  },
+  "types": "./index.d.ts",
+  "keywords": [
+    "intl",
+    "date",
+    "javascript",
+    "i18n",
+    "timezone",
+    "creowis"
+  ],
+  "license": "MIT",
+  "engines": {
+    "node": ">=18"
+  },
+  "devDependencies": {
+    "esbuild": "^0.21.0"
+  }
+}

package/src/dateUtils.js

@@ -0,0 +1,280 @@
+// dateUtils.js
+// Modern Intl-based date utilities
+// Zero dependencies. Node 18+ and modern browsers.
+
+// ─────────────────────────────────────────────
+// Internal Helpers
+// ─────────────────────────────────────────────
+
+function toDate(value) {
+  const d = value instanceof Date ? value : new Date(value)
+
+  if (Number.isNaN(d.getTime())) {
+    throw new Error(`Invalid date value: ${value}`)
+  }
+
+  return d
+}
+
+// ─────────────────────────────────────────────
+// Intl Formatter Cache
+// ─────────────────────────────────────────────
+
+const formatterCache = new Map()
+
+function getFormatter(locale, options) {
+  const key = locale + "|" + JSON.stringify(options)
+
+  if (!formatterCache.has(key)) {
+    formatterCache.set(key, new Intl.DateTimeFormat(locale, options))
+  }
+
+  return formatterCache.get(key)
+}
+
+// ─────────────────────────────────────────────
+// Core Formatting Utilities
+// ─────────────────────────────────────────────
+
+function formatDate(date, locale = "en-US", style = "medium") {
+  return getFormatter(locale, { dateStyle: style }).format(toDate(date))
+}
+
+function formatTime(date, locale = "en-US", style = "short") {
+  return getFormatter(locale, { timeStyle: style }).format(toDate(date))
+}
+
+function formatDateTime(date, locale = "en-US", options = {}) {
+  const { dateStyle = "medium", timeStyle = "short", timeZone } = options
+
+  return getFormatter(locale, {
+    dateStyle,
+    timeStyle,
+    timeZone
+  }).format(toDate(date))
+}
+
+function formatInTimezone(date, timeZone, locale = "en-US") {
+  return getFormatter(locale, {
+    dateStyle: "long",
+    timeStyle: "short",
+    timeZone
+  }).format(toDate(date))
+}
+
+// ─────────────────────────────────────────────
+// ISO Calendar Date
+// Useful for cross-timezone comparisons
+// ─────────────────────────────────────────────
+
+function toLocaleDateISO(date, timeZone = "UTC") {
+  const fmt = getFormatter("en-CA", {
+    year: "numeric",
+    month: "2-digit",
+    day: "2-digit",
+    timeZone
+  })
+
+  const parts = Object.fromEntries(
+    fmt.formatToParts(toDate(date)).map(p => [p.type, p.value])
+  )
+
+  return parts.year + "-" + parts.month + "-" + parts.day
+}
+
+// ─────────────────────────────────────────────
+// Relative Time
+// ─────────────────────────────────────────────
+
+const rtfCache = new Map()
+
+function getRTF(locale, numeric = "auto") {
+  const key = locale + "|" + numeric
+
+  if (!rtfCache.has(key)) {
+    rtfCache.set(key, new Intl.RelativeTimeFormat(locale, { numeric }))
+  }
+
+  return rtfCache.get(key)
+}
+
+const RELATIVE_UNITS = [
+  ["year", 31536000],
+  ["month", 2592000],
+  ["week", 604800],
+  ["day", 86400],
+  ["hour", 3600],
+  ["minute", 60],
+  ["second", 1]
+]
+
+function timeAgo(date, locale = "en") {
+  const diffSeconds = (toDate(date).getTime() - Date.now()) / 1000
+  const abs = Math.abs(diffSeconds)
+
+  const rtf = getRTF(locale)
+
+  for (const [unit, seconds] of RELATIVE_UNITS) {
+    if (abs >= seconds) {
+      return rtf.format(Math.round(diffSeconds / seconds), unit)
+    }
+  }
+
+  return rtf.format(0, "second")
+}
+
+// ─────────────────────────────────────────────
+// Calendar Helpers
+// ─────────────────────────────────────────────
+
+function getMonthNames(locale = "en-US", style = "long") {
+  const fmt = getFormatter(locale, { month: style })
+
+  return Array.from({ length: 12 }, (_, i) =>
+    fmt.format(new Date(2026, i, 1))
+  )
+}
+
+function getDayNames(locale = "en-US", style = "long", startDay = 0) {
+  const fmt = getFormatter(locale, { weekday: style })
+
+  return Array.from({ length: 7 }, (_, i) =>
+    fmt.format(new Date(2026, 0, 4 + startDay + i))
+  )
+}
+
+// ─────────────────────────────────────────────
+// Date Range Formatting
+// ─────────────────────────────────────────────
+
+function formatRange(start, end, locale = "en-US", style = "long") {
+  const fmt = getFormatter(locale, { dateStyle: style })
+
+  return fmt.formatRange(toDate(start), toDate(end))
+}
+
+// ─────────────────────────────────────────────
+// Date Comparison Helpers
+// ─────────────────────────────────────────────
+
+function sameCalendarDate(a, b) {
+  return (
+    a.getFullYear() === b.getFullYear() &&
+    a.getMonth() === b.getMonth() &&
+    a.getDate() === b.getDate()
+  )
+}
+
+function isToday(date) {
+  return sameCalendarDate(toDate(date), new Date())
+}
+
+function isYesterday(date) {
+  const today = startOfDay(new Date())
+  const yesterday = addDays(today, -1)
+
+  return sameCalendarDate(toDate(date), yesterday)
+}
+
+function isTomorrow(date) {
+  const today = startOfDay(new Date())
+  const tomorrow = addDays(today, 1)
+
+  return sameCalendarDate(toDate(date), tomorrow)
+}
+
+// ─────────────────────────────────────────────
+// Date Math Utilities
+// ─────────────────────────────────────────────
+
+function startOfDay(date) {
+  const d = toDate(date)
+  return new Date(d.getFullYear(), d.getMonth(), d.getDate())
+}
+
+function endOfDay(date) {
+  const d = toDate(date)
+  return new Date(d.getFullYear(), d.getMonth(), d.getDate(), 23, 59, 59, 999)
+}
+
+function addDays(date, amount) {
+  const d = toDate(date)
+  const result = new Date(d)
+  result.setDate(result.getDate() + amount)
+  return result
+}
+
+function addMonths(date, amount) {
+  const d = toDate(date)
+  const result = new Date(d)
+  result.setMonth(result.getMonth() + amount)
+  return result
+}
+
+function differenceInDays(a, b) {
+  const diff =
+    startOfDay(toDate(a)).getTime() - startOfDay(toDate(b)).getTime()
+
+  return Math.round(diff / 86400000)
+}
+
+// ─────────────────────────────────────────────
+// ISO Parsing
+// ─────────────────────────────────────────────
+
+function parseISO(value) {
+  const d = new Date(value)
+
+  if (Number.isNaN(d.getTime())) {
+    throw new Error(`Invalid ISO date: ${value}`)
+  }
+
+  return d
+}
+
+// ─────────────────────────────────────────────
+// Smart UI Formatting
+// Perfect for feeds / dashboards
+// ─────────────────────────────────────────────
+
+function formatSmartDate(date, locale = "en-US") {
+  const d = toDate(date)
+
+  if (isToday(d)) {
+    return "Today " + formatTime(d, locale)
+  }
+
+  if (isYesterday(d)) {
+    return "Yesterday"
+  }
+
+  const diff = Math.abs(Date.now() - d.getTime())
+
+  if (diff < 7 * 86400000) {
+    return timeAgo(d, locale)
+  }
+
+  return formatDate(d, locale, "medium")
+}
+
+export {
+  addDays,
+  addMonths,
+  differenceInDays,
+  endOfDay,
+  formatDate,
+  formatDateTime,
+  formatInTimezone,
+  formatRange,
+  formatSmartDate,
+  formatTime,
+  getDayNames,
+  getMonthNames,
+  isToday,
+  isTomorrow,
+  isYesterday,
+  parseISO,
+  startOfDay,
+  timeAgo,
+  toLocaleDateISO
+};

package/src/index.d.ts

@@ -0,0 +1,84 @@
+export function formatDate(
+  date: Date | number | string,
+  locale?: string,
+  style?: 'full' | 'long' | 'medium' | 'short'
+): string
+
+export function formatTime(
+  date: Date | number | string,
+  locale?: string,
+  style?: 'full' | 'long' | 'medium' | 'short'
+): string
+
+export function formatDateTime(
+  date: Date | number | string,
+  locale?: string,
+  options?: {
+    dateStyle?: 'full' | 'long' | 'medium' | 'short'
+    timeStyle?: 'full' | 'long' | 'medium' | 'short'
+    timeZone?: string
+  }
+): string
+
+export function formatInTimezone(
+  date: Date | number | string,
+  timeZone: string,
+  locale?: string
+): string
+
+export function toLocaleDateISO(
+  date: Date | number | string,
+  timeZone?: string
+): string
+
+export function timeAgo(
+  date: Date | number | string,
+  locale?: string
+): string
+
+export function getMonthNames(
+  locale?: string,
+  style?: 'long' | 'short' | 'narrow'
+): string[]
+
+export function getDayNames(
+  locale?: string,
+  style?: 'long' | 'short' | 'narrow',
+  startDay?: number
+): string[]
+
+export function formatRange(
+  start: Date | number | string,
+  end: Date | number | string,
+  locale?: string,
+  style?: 'full' | 'long' | 'medium' | 'short'
+): string
+
+export function isToday(date: Date | number | string): boolean
+export function isYesterday(date: Date | number | string): boolean
+export function isTomorrow(date: Date | number | string): boolean
+
+export function startOfDay(date: Date | number | string): Date
+export function endOfDay(date: Date | number | string): Date
+
+export function addDays(
+  date: Date | number | string,
+  amount: number
+): Date
+
+export function addMonths(
+  date: Date | number | string,
+  amount: number
+): Date
+
+export function differenceInDays(
+  a: Date | number | string,
+  b: Date | number | string
+): number
+
+export function parseISO(value: string): Date
+
+export function formatSmartDate(
+  date: Date | number | string,
+  locale?: string
+): string

package/tests/dateUtils.test.js

@@ -0,0 +1,248 @@
+import test from "node:test"
+import assert from "node:assert/strict"
+
+import {
+  formatDate,
+  formatTime,
+  formatDateTime,
+  formatInTimezone,
+  toLocaleDateISO,
+  timeAgo,
+  getMonthNames,
+  getDayNames,
+  formatRange,
+  isToday,
+  isYesterday,
+  isTomorrow,
+  startOfDay,
+  endOfDay,
+  addDays,
+  addMonths,
+  differenceInDays,
+  parseISO,
+  formatSmartDate
+} from "../src/dateUtils.js"
+
+const sampleDate = new Date("2026-03-15T14:30:00Z")
+
+// ---------------------------------------------------
+// formatDate
+// ---------------------------------------------------
+
+test("formatDate returns formatted date string", () => {
+  const result = formatDate(sampleDate, "en-US", "long")
+  assert.equal(typeof result, "string")
+  assert.ok(result.includes("2026"))
+})
+
+// ---------------------------------------------------
+// formatTime
+// ---------------------------------------------------
+
+test("formatTime returns formatted time", () => {
+  const result = formatTime(sampleDate, "en-US")
+  assert.equal(typeof result, "string")
+})
+
+// ---------------------------------------------------
+// formatDateTime
+// ---------------------------------------------------
+
+test("formatDateTime formats date and time", () => {
+  const result = formatDateTime(sampleDate, "en-US")
+  assert.equal(typeof result, "string")
+})
+
+// ---------------------------------------------------
+// formatInTimezone
+// ---------------------------------------------------
+
+test("formatInTimezone formats date in provided timezone", () => {
+  const result = formatInTimezone(sampleDate, "Asia/Tokyo")
+  assert.equal(typeof result, "string")
+})
+
+// ---------------------------------------------------
+// toLocaleDateISO
+// ---------------------------------------------------
+
+test("toLocaleDateISO returns YYYY-MM-DD format", () => {
+  const result = toLocaleDateISO(sampleDate)
+  assert.match(result, /^\d{4}-\d{2}-\d{2}$/)
+})
+
+// ---------------------------------------------------
+// timeAgo
+// ---------------------------------------------------
+
+test("timeAgo returns relative time string", () => {
+  const past = addDays(new Date(), -2)
+  const result = timeAgo(past)
+
+  assert.equal(typeof result, "string")
+})
+
+// ---------------------------------------------------
+// getMonthNames
+// ---------------------------------------------------
+
+test("getMonthNames returns 12 months", () => {
+  const months = getMonthNames()
+
+  assert.equal(months.length, 12)
+  assert.equal(typeof months[0], "string")
+})
+
+// ---------------------------------------------------
+// getDayNames
+// ---------------------------------------------------
+
+test("getDayNames returns 7 day names", () => {
+  const days = getDayNames()
+
+  assert.equal(days.length, 7)
+  assert.equal(typeof days[0], "string")
+})
+
+// ---------------------------------------------------
+// formatRange
+// ---------------------------------------------------
+
+test("formatRange returns formatted range string", () => {
+  const start = new Date("2026-03-10")
+  const end = new Date("2026-03-15")
+
+  const result = formatRange(start, end)
+
+  assert.equal(typeof result, "string")
+})
+
+// ---------------------------------------------------
+// startOfDay
+// ---------------------------------------------------
+
+test("startOfDay resets time to midnight", () => {
+  const d = startOfDay(sampleDate)
+
+  assert.equal(d.getHours(), 0)
+  assert.equal(d.getMinutes(), 0)
+})
+
+// ---------------------------------------------------
+// endOfDay
+// ---------------------------------------------------
+
+test("endOfDay sets time to end of day", () => {
+  const d = endOfDay(sampleDate)
+
+  assert.equal(d.getHours(), 23)
+  assert.equal(d.getMinutes(), 59)
+})
+
+// ---------------------------------------------------
+// addDays
+// ---------------------------------------------------
+
+test("addDays correctly adds days", () => {
+  const d = new Date("2026-03-10")
+
+  const result = addDays(d, 5)
+
+  assert.equal(result.getDate(), 15)
+})
+
+// ---------------------------------------------------
+// addMonths
+// ---------------------------------------------------
+
+test("addMonths correctly adds months", () => {
+  const d = new Date("2026-01-10")
+
+  const result = addMonths(d, 2)
+
+  assert.equal(result.getMonth(), 2)
+})
+
+// ---------------------------------------------------
+// differenceInDays
+// ---------------------------------------------------
+
+test("differenceInDays calculates difference correctly", () => {
+  const a = new Date("2026-03-15")
+  const b = new Date("2026-03-10")
+
+  const diff = differenceInDays(a, b)
+
+  assert.equal(diff, 5)
+})
+
+// ---------------------------------------------------
+// parseISO
+// ---------------------------------------------------
+
+test("parseISO parses ISO string correctly", () => {
+  const d = parseISO("2026-03-15")
+
+  assert.ok(d instanceof Date)
+  assert.equal(d.getFullYear(), 2026)
+})
+
+test("parseISO throws for invalid date", () => {
+  assert.throws(() => parseISO("invalid-date"))
+})
+
+// ---------------------------------------------------
+// isToday
+// ---------------------------------------------------
+
+test("isToday detects today", () => {
+  const today = new Date()
+
+  assert.equal(isToday(today), true)
+})
+
+// ---------------------------------------------------
+// isYesterday
+// ---------------------------------------------------
+
+test("isYesterday detects yesterday", () => {
+  const yesterday = addDays(new Date(), -1)
+
+  assert.equal(isYesterday(yesterday), true)
+})
+
+// ---------------------------------------------------
+// isTomorrow
+// ---------------------------------------------------
+
+test("isTomorrow detects tomorrow", () => {
+  const tomorrow = addDays(new Date(), 1)
+
+  assert.equal(isTomorrow(tomorrow), true)
+})
+
+// ---------------------------------------------------
+// formatSmartDate
+// ---------------------------------------------------
+
+test("formatSmartDate returns today format", () => {
+  const result = formatSmartDate(new Date())
+
+  assert.ok(result.startsWith("Today"))
+})
+
+test("formatSmartDate returns yesterday string", () => {
+  const yesterday = addDays(new Date(), -1)
+
+  const result = formatSmartDate(yesterday)
+
+  assert.equal(result, "Yesterday")
+})
+
+test("formatSmartDate returns formatted date for older dates", () => {
+  const oldDate = addDays(new Date(), -10)
+
+  const result = formatSmartDate(oldDate)
+
+  assert.equal(typeof result, "string")
+})