turning js files into ts causes many eslint errors

[markgoho]

Current Behavior

eslint complaining about a lot of issues after all the jest config files were converted to typescript files

Expected Behavior

changing file formats should also come with updated linting rules

Steps to Reproduce

nx migrate latest (14.0.3)

You can clone the repo and check out the nx-14 branch:
https://github.com/ideacrew/active-branch-tracker/tree/nx-14

Failure Logs

mostly it's the 'ts-jest' property and the pattern-matching property that ESLint is complaining about.

Environment

Win 11
Node 14
Nx 14.0.3

Additional failures that probably need addressing as well

In typescript files, module.exports isn't the preferred way to export things

[AgentEnder]

@barbados-clemens could we update the migration to add an eslint ignore comment?

[markgoho]

@AgentEnder great idea!

any thoughts about exporting the module in a more TypeScript-y way?

export default { }

[barbados-clemens]

@markgoho ideally yes. it's just a big upshift to make. I have plans to move new jest projects to export default. but I'm slightly apprehensive to move existing configurations to different syntax to not break even more things.

[barbados-clemens]

after about 20 minutes of thinking of this. I'll do the migration for export default
mainly because using the nxPreset from @nrwl/jest/preset is also breaking things in the nx repo and moving all to default exports fixes this issue.

hope to have a PR up some time tomorrow.

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.