Skip to content

chore: support extensionless TypeScript imports #45

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AbdelrahmanBayoumi merged 2 commits into from
Nov 4, 2026
Merged

chore: support extensionless TypeScript imports #45

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9e4128b
chore: support extensionless imports with tsdown
AbdelrahmanBayoumi Nov 3, 2026
1e9b4db
chore: clarify type imports and ESM build config
AbdelrahmanBayoumi Nov 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@
## [Unreleased]

### Added
- Extensionless static relative imports and directory barrels in TypeScript source builds, with NodeNext-compatible ESM JavaScript and declarations.
- Technical articles explaining Arabic affix removal and banned-word matching, including design decisions, examples, and known limitations.
- Integration tests for CJS, ESM, and browser UMD artifacts.
- Arabic NLP boundary and ReDoS resilience test suites.
Expand Down
1 change: 1 addition & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,7 @@ Before submitting a Pull Request, please ensure:
npm test
```
`npm test` runs source tests, builds the package once, then checks the compiled artifacts.
CommonJS output retains extensionless relative specifiers for Node.js to resolve; the unbundled ESM build uses tsdown to emit Node.js-compatible `.js` specifiers and declarations. Webpack handles source resolution for the browser bundles.
Use `npm run test:unit` (or `npm run test:watch`) during development without building.
After an existing build, use `npm run test:artifacts` to check CJS/ESM/UMD consumers, npm package contents, source maps, and real bundle tree shaking. It reports minified sizes for a single-function consumer and the full object; results depend on the imports and installed bundler version.
Add focused source regression tests for new logic or bug fixes, and artifact tests for packaging or export changes.
Expand Down
Loading
Loading