# Is is possible to specify the \`tsconfig\` file with the Forge CLI? **URL:** \ **Category:** Forge Platform and Tools\ **Tags:** typescript, forge-cli, forge-lint, forge\ **Created:** [January 16, 2022, 10:45am UTC](https://community.developer.atlassian.com/t/is-is-possible-to-specify-the-tsconfig-file-with-the-forge-cli/55111 "2022-01-16T10:45:34Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![scott.dudley](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/scott.dudley/32/53884_2.png) [@scott.dudley](https://community.developer.atlassian.com/u/scott.dudley)\ **Post date:** [January 17, 2022, 6:47pm UTC](https://community.developer.atlassian.com/t/is-is-possible-to-specify-the-tsconfig-file-with-the-forge-cli/55111/3 "2022-01-17T18:47:46Z")
Although this does not solve your problem, you might find it helpful to see the following post describing some of the mechanics of how TS is used in the build process (including in “forge tunnel”): > [@Using alternate version of TypeScript](https://community.developer.atlassian.com/t/using-alternate-version-of-typescript/53002): > > Hi Forge team, Is there any supported mechanism planned for using an alternate version of TypeScript? I have an existing codebase running on TS 4.4 that I am trying to get to build on Forge, but it is…not easy. I was able to hack it into a working state, but I wouldn’t want to ship anything with this amount of duct tape. This creates a blocker for anyone who has a project built with a newer version of TS than yours, but who cannot (or doesn’t want to) backport the entire project syntax to an e… --- _[View the full topic](https://community.developer.atlassian.com/t/is-is-possible-to-specify-the-tsconfig-file-with-the-forge-cli/55111)._