-
Notifications
You must be signed in to change notification settings - Fork 921
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WORKSPACE] Bit status how to not be aware of some import s #8818
Comments
it is really not recommended for components to import internal files or self-refer to the package name. this may cause compilation issues down the line. if you want Bit to stop complaining on some issues, you can add a similar config to your
all possible issues are here - https://github.com/teambit/bit/tree/master/components/component-issues |
In addition to what @itaymendel wrote. |
Hello ! Sorry and thanks for the informations but in fact we were looking for a backend solution of monorepo workspace management, and found BIT on the pnpm docs It's not very clear for us what our apps and packages can be related to BIT, but if we understood correctly anything can be a component. So does that means Bit is not for backend typescript project ? In fact we are using In fact to resume we just need Bit as a workspace dependencies management (and it shine wth bit status, bit show ...), not really for component compile .. (we will continue to compile our backend app via TSC etc ..) |
Bit doesn't support ts paths between components, as they are related to the specific file system structure of the workspace, and locks you to a specific FS structure. In bit, each component is automatically linked via node-modules, and you are expected to use these module links. |
Description
In our project (backend) we are using aliased to import files, that means not relative.
So our packages/core/index.ts folder can import something via
import {} from '@ava/core/helper'
This lead bit status to indicated us we have issue with import, causing a lot of noises and prevent us to see the real missing dependencies.
How could we deal with that ?
Same question but seems when we don't import main file it's not ok too, we have
packages
folder that just represent a group of file that could be imported directly by our backendSpecifications
Context and additional information
The text was updated successfully, but these errors were encountered: