Describe the bug
Doc site shows npm install --save luxon when it should be npm install --save ts-luxon

I'd put in a PR myself but I couldn't find where the docs were located here or in your portfolio repo (repo looks to be bundled for prod prior to push unlike the old/ directory of your previous portfolio).

Just had to add that I really appreciate your TypeScript conversion of the repo since the DefinitelyTyped @types/luxon does not contain the complete types (ex. properties on the DateTime object).

Describe the bug

import { DateTime } from 'ts-luxon';
         ^^^^^^^^
SyntaxError: The requested module 'ts-luxon' does not provide an export named 'DateTime'

ts-luxon needs to have a properly declared exports field in package.json for Node to use the ESM bundle. Additionally, the exports need to have the correct file extension to avoid incorrect interpretation.

Example:

{
    "type": "commonjs",
    "exports": {
        ".": {
            "types": "./dist/index.d.ts",
            "import": "./dist/ts-luxon.es6.mjs", // NOTE: .mjs file extension
            "default": "./dist/ts-luxon.umd.js" // NOTE: interpreted as commonjs due to `type` field
        }
    }
}

Note that the example has this issue.
See: https://publint.dev/[email protected]

To Reproduce
https://stackblitz.com/edit/stackblitz-starters-gpzsez?file=index.js

Actual vs Expected behavior
No import errors.

Desktop (please complete the following information):

• OS: Windows 11
• Browser: Chrome 125.0.6368.2 (Official Build) dev (64-bit)
• Luxon version: 4.5.2

The API docs links at the bottom of this page link to https://tonysamperi.github.io/ts-luxon/docs/api-docs/index.html however this link is a 404.

Would it be possible to add the following functions to the library?

• isFuture
• isPast
• isTheSameDay
• isTheSameMonth
• isTheSameYear

These last 3 should compare the day, month, and year as a whole

Thanks in advance!

Describe the issue
The documentation of some methods - listed below - does not match the implementation. The documentation lists one can pass @param {boolean} [options.nullOnInvalid=false] - return null on invalid values instead of throwing an error; however, this property does not exist on the type of DateTimeOptions which is used to type the [options|opts] parameter used in most DateTime class methods.

Instances of [options|opts].nullOnInvalid being referenced

• DateTime.diff()
• DateTime.fromSeconds()
• DateTime.fromJSDate()
• DateTime.fromMillis()

Describe the bug
After the last update of Chromium 110, generated Dates with Meridiem can't be parsed correctly due to NNBSP

see tonysamperi/ngx-mat-timepicker#51

To Reproduce

    const dto = DateTime.fromFormat("3:22 AM", "h:m a", {
        numberingSystem: "latn",
        locale: "en-US"
    });

Actual vs Expected behavior
dto is expected to be valid, but it is invalid due to parse error

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser: all chromium based browsers above v 109
• ts-luxon version: 4.0.0 (but every version is affected)

Describe the bug
There are missing files errors in the build log.

WARNING in ../node_modules/ts-luxon/dist/ts-luxon.es6.js
Module Warning (from ../node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from 'node_modules/src/zones/fixedOffsetZone.ts' file: Error: ENOENT: no such file or directory, open...

To Reproduce
Build the project with newest [email protected]

Actual vs Expected behavior
Build without warnings and errors.

Desktop (please complete the following information):

• OS: Ubuntu
• Browser Crome
• Luxon version 4.2.2

Additional context
It was not there before the bugfix. I am doing weekly updates.

In the package json it says:

"typings": "dist/index.d.ts",

but in 4.3.0 the actual index.d.ts has been moved to here:

"dist/lib/index.d.ts"

Without adjusting the package.json information.

This leads to the following error in our builds: error TS7016: Could not find a declaration file for module 'ts-luxon'

Hi @tonysamperi,

Firstly, congratulations on this great work; ts-luxon is truly amazing.

I feel that a date library like ts-luxon is missing in the Deno ecosystem. It would be great if you could consider sharing your library on Deno Land.

Deno + TS-Luxon is the perfect combination, and you could make this possible.

Thanks in advance!