Bit's Gitter channel. Feel free to ask anything, help others and have fun. https://bit.dev
Hi!
I have a question about reusing components, using the bit client.
Let's say I have a project, where i bit init and then bit import ... a component.
After that I push this project to a git repo. I include only my code using the component, .bitmap and package.json, which retain the workspace configuration. I left out the components directory, as specified in documentation under "Best practices".
I now try to clone this project and get it up and running.
As I understand, when I run bit import in the cloned repo, all components should be made available. But I see no components directory is created, so I can't use the components unless I bit import every component by it self again.
What am I doing wrong?
bit status gives me the error that "component files were deleted".
But I guess that is to be expected, as I don't have a component directory
@itaymendel_twitter I see now that this is the default behaviour for bit import without giving any ids. It just imports component objects, but don't write anything to the file system.
Then I wonder, what would be the correct way to do this without committing the components directory?
Thank you for your help! :)
bit import ... --extension command inside such a remote, I only get a message telling my it's not a workspace.~/d/c/t/bit-remote ❯❯❯ bit init --bare
successfully initialized an empty bare bit scope.
~/d/c/t/bit-remote ❯❯❯ bit import
workspace not found. to initiate a new workspace, please use `bit init`
~/d/c/t/bit-remote ❯❯❯
on our server, we import the webhook extension to some folder (doesn't really matter where)bit import bit.extensions/defaults/webhooks@0.2.1 --extension
than we configure the global bit.json like this
{
"extensions": {
"bit.extensions/defaults/webhooks@0.2.1": {
"config": {
"publisherBaseUrl": "some url"
},
"options": {
"file": "path to imported location/components/defaults/webhooks/bit.extensions/0.2.1/index.js"
}
}
}
}the global bit.json is located at/root/Library/Caches/Bit/config/bit.json
(assuming it's a linux machine) - it might not be existing, you can create it
then run some operation (can bit a bit list against the remote) and look on the logs in the server to check if the extension loaded correctly
bit npm-pack which creates the tar file
you can see an example (it's not documented as well since it's not fully tested)
https://github.com/teambit/bit/blob/060ae2f58226637ee5ed96342b5edf2e464c7a6c/e2e/npm-ci-registry.ts
this is taken from bit e2e tests, where we run our own registry with different scope name
Also would be really like to hear your story when you success:)
error: component "fc.lib/ui/label@0.0.1" was not found
`$ bit list
- listing components
found 0 components in local scope
`
It fails in a normal JSX prop..
error: bit failed to build button with the following exception:
unknown: Unexpected token, expected "," (14:4)
12 | export const primary = () => (
13 | <Button14 | disabled={boolean('Disabled', false)}
| ^
15 | block={boolean('Block', false)}
16 | >
My current babelrc file lists: "presets": ["flow", "@babel/preset-flow", "@babel/preset-env", "@babel/preset-react"] whereas the flow compiler lists: "presets": ["@babel/preset-env","@babel/preset-flow"],
But since I am new to Bit, I am still not sure that this will be fixed only by changing the presets.
"@babel/preset-react" and it seems to have worked in the build!https://bit.dev/diego-caceres/compilers/compilers/flow