Create a component modifies tsconfig.json

[UrielZohar]

I just ran -

bit create react hello-world

and it's effected the files-

.eslintrc.json, .prettierrc.cjs and tsconfig.json

How can I just create the component without modify those file ?

[davidfirst]

Thanks for reporting this, and sorry for the slow reply.

Some background: bit writes IDE config files (tsconfig.json, .eslintrc.json, .prettierrc.cjs) into the workspace so your IDE picks up the env configuration of each component. The gap was that when such a file was already in the workspace, bit treated it as its own and rewrote it. A file that you wrote should stay yours — and now it does. I reproduced what you saw before fixing it.

A few things worth knowing:

• A PR merged the same day you opened this discussion (feature(ws-config) - new componentsRootDir, useDefaultDirectory config #9824) added the componentsRootDir and useDefaultDirectory options. When you set a default directory for your components, bit writes its config files no higher than that directory, so the workspace root stays yours.
• This also doesn't happen when you run bit init in a directory that already has .git. Init then asks a few questions and sets the default directory to bit-components/{scope}/{name}, which turns on the same protection.

That left the case you ran into: a workspace whose default directory starts with a dynamic segment, which is the plain default.

#10701 now covers this regardless of the configuration. Before bit writes a config file, it checks the comment at the top of the existing file to see whether bit generated it. If the file is yours, bit keeps it and lists what it skipped:

⚠ config files not overridden (2)
  these files already exist and were not generated by bit, so they were left untouched.
  to have bit write them, delete them first or run "bit ws-config write --force".
   › tsconfig.json
   › .prettierrc.cjs

If you'd like bit to manage these files after all, run bit ws-config write --force.

A new version with this fix will be released tonight.

And if you'd rather bit didn't write these files at all, you can turn it off in workspace.jsonc:

"teambit.workspace/workspace-config-files": { "enableWorkspaceConfigWrite": false }