Replies: 1 comment
|
Hi @utillity, sorry this sat unanswered for so long. There are two different sources of 1. Files that shouldn't be part of the component at all( Use a One gotcha worth knowing: if a There's a config equivalent if you'd rather keep it in one place: // workspace.jsonc
"teambit.workspace/workspace": {
"ignoredFiles": ["**/obj/**", "**/bin/**"]
}2. Files that must stay in the component, but whose imports bit shouldn't try to resolveThis is likely your actual case — the transpiled JS/TS needs to ship, but bit's dependency Make this the very first thing in the file: // @bit-no-checkbit then skips dependency detection for that file entirely. It's a literal "starts with" If it's only a couple of imports rather than the whole file, If neither of those covers your case, paste your |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
One of our components is actually written in F# and transpiled to Javascript and Typescript. So I would like to exclude these directories from code-analysis, as ie.
bit statusgenerates a lot of noise.All reactions