Fix ERR_UNKNOWN_FILE_EXTENSION error when running TypeScript files with ts-node in ESM mode #327
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When attempting to start the application with
yarn startoryarn start-backend, the build fails with the following error:This error occurs because the project has
"type": "module"inpackage.json, which enables ES modules mode in Node.js. When running TypeScript files withts-nodein ESM mode, Node.js doesn't recognize the.tsfile extension without proper loader configuration.Solution
This PR fixes the issue by configuring Node.js to use the ts-node ESM loader when executing TypeScript files:
nodemon.json - Added
execMapconfiguration to tell nodemon how to execute.tsfiles:package.json - Updated the
build-staticscript to use the loader directly since it bypasses nodemon:Testing
Verified that the following commands now work correctly:
yarn start- Both backend server and frontend webpack build successfullyyarn start-backend- Backend server starts on port 3000yarn build-static- Executes without errors (fails with expected config error, not file extension error)The application now starts successfully and displays:
Note: The
ExperimentalWarningabout--experimental-loaderis expected behavior from Node.js and doesn't affect functionality. The test script (yarn test) already had proper loader configuration via ts-mocha and continues to work correctly.Closes #[issue_number]
Original prompt
Fixes #326
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.