chore: fix tsconfig.json to include .js and .ts files in src dir

[lumirlumir]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request?

In this PR, I’ve updated the tsconfig.json file to include all .js and .ts files in the src directory.

Previously, due to the changes introduced in #383, type checking was only applied to src/index.js, and the rest of the src directory was skipped. As a result, newly added rules and other files did not benefit from type checking.

Here’s a minimal way to reproduce the issue:

• Create a test.js file at src/rules/test.js:

  

  The Set doesn’t have a push method, but type checking doesn’t catch this error.

• After updating the tsconfig.json:

  

  Type checking works as intended.

What changes did you make? (Give an overview)

Related Issues

Is there anything you'd like reviewers to focus on?

[lumirlumir]

If we use the files field, glob patterns are not supported.

[snitin315]

This has changed the dist directory structure.

Before

After

[snitin315]

So the package export's aren't valid anymore:

markdown/package.json

Lines 11 to 24 in 589323f

	"main": "dist/esm/index.js",
	"types": "dist/esm/index.d.ts",
	"exports": {
	".": {
	"types": "./dist/esm/index.d.ts",
	"default": "./dist/esm/index.js"
	},
	"./types": {
	"types": "./dist/esm/types.d.ts"
	}
	},
	"files": [
	"dist"
	],

[lumirlumir]

@snitin315 Thanks for sharing the context.

However, the changes you mentioned originate from #383, not from this PR. (I believe the latest changes from #383 are not yet reflected in your local environment.)

Even if we revert the changes in this PR, the dist folder remains the same — the differences shown in your screenshot are due to #383.

So the package exports aren't valid anymore:

That’s exactly why #383 was marked as a breaking change — the file structure in the dist folder was changed in that PR.

[snitin315]

Ah! Got it, thanks for the explanation. My local main branch was outdated.