ektotv / xmltv Goto Github PK

When I attempt to import the package into my TypeScript project using

import { parseXmltv } from "@iptv/xmltv"

I get the following error:

Could not find a declaration file for module '@iptv/xmltv'. 'c:/Users/***/Documents/my-application/node_modules/@iptv/xmltv/dist/xmltv.js' implicitly has an 'any' type.
  There are types at 'c:/Users/***/Documents/my-application/node_modules/@iptv/xmltv/dist/index.d.ts', but this result could not be resolved when respecting package.json "exports". The '@iptv/xmltv' library may need to update its package.json or typings.ts(7016)

I found this in the TypeScript documentation while searching for a solution:

It’s important to note that the CommonJS entrypoint and the ES module entrypoint each needs its own declaration file, even if the contents are the same between them. Every declaration file is interpreted either as a CommonJS module or as an ES module, based on its file extension and the "type" field of the package.json, and this detected module kind must match the module kind that Node will detect for the corresponding JavaScript file for type checking to be correct. Attempting to use a single .d.ts file to type both an ES module entrypoint and a CommonJS entrypoint will cause TypeScript to think only one of those entrypoints exists, causing compiler errors for users of the package
(https://www.typescriptlang.org/docs/handbook/esm-node.html)

Unfortunately with the last release v0.1.4 the parsing of ISO substrings is broken.
The date property of a program can be one of:

1. YYYY (2021)
2. YYYYMM (202105)
3. YYYYMMDD (20210515)

All dates and times in this DTD follow the same format, loosely based
on ISO 8601. They can be 'YYYYMMDDhhmmss' or some initial
substring, for example if you only know the year and month you can
have 'YYYYMM'. You can also append a timezone to the end; if no
explicit timezone is given, UTC is assumed. Examples:
'200007281733 BST', '200209', '19880523083000 +0300'. (BST == +0100.)

Thx for the tooling