Why is there a old tsconfig.json file injected to my repo?

Replit Help
,
1

This repo has no tsconfig.json file at it’s root. Yet, when loaded into Replit, it will create one with really old conflicting settings that cause TSC to fail.

I tried using onBoot to delete it, but that doesn’t run immediately after a clone, only after a restart.

Screenshot from 2023-04-29 09-02-53
Screenshot from 2023-04-29 09-02-53787×495 42.6 KB

Is there any way to force Replit to give me a normal plain Bash container as the base instead of an outdated Node v16 container with bad config files? For some reason loading this on mobile also tries to open a non existent index.ts file.

2

Works fine for me :thinking: What do you try to do, and what do you expect to happen?

2 Likes
3

It works “fine” due to a number of hacky acrobatics in my .replit script… Mainly I added rm tsconfig.json to the compile script.

That only works if you use the run button instead of the provided Shell as I show in the screenshot. There is no reason why node --version should trigger a container restart.