fix: export type information for node16 module resolution#28
fix: export type information for node16 module resolution#28RebeccaStevens wants to merge 1 commit intojonschlinkert:masterfrom
Conversation
RebeccaStevens
force-pushed
the
node16-types-exports
branch
3 times, most recently
from
6db0155 to
c00f8d4
Compare
RebeccaStevens
force-pushed
the
node16-types-exports
branch
from
c00f8d4 to
1cc2106
Compare
|
I was about to create a PR for this, but @RebeccaStevens has done a great job here already. |
|
@jonschlinkert @TrySound Is there any chance to move this forward? This blocks people using TS ESM with is-plain-object. |
|
@jonschlinkert is this library unmaintained? |
|
Just ran into this issue when migrating a codebase to Anyone know of an alternative NPM package that you can use to resolve this issue? Otherwise I'll just fork this one, fix the issue and publish to NPM. |
|
https://github.com/sindresorhus/is-plain-obj works well with TypeScript ESM. |
Summary: - Rewrite TypeScript definitions to use ESM syntax, avoiding the specific syntax like `namespace`. - Update `tsconfig.json` for ESM and Node.js 18. - Remove no longer needed `test.d.ts`. - Add a patch for the `is-plain-object` package to avoid type-check errors. See also: - https://www.typescriptlang.org/tsconfig - https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#package-json-exports-imports-and-self-referencing - jonschlinkert/is-plain-object#28
Summary: - Rewrite TypeScript definitions to use ESM syntax, avoiding the specific syntax like `namespace`. - Update `tsconfig.json` for ESM and Node.js 18. - Remove no longer needed `test.d.ts`. - Add a patch for the `is-plain-object` package to avoid type-check errors. See also: - https://www.typescriptlang.org/tsconfig - https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#package-json-exports-imports-and-self-referencing - jonschlinkert/is-plain-object#28
5 participants
See TS 4.7-rc Release Notes for details.