bit src/Bit

This channle is no longer supported. we have moved to Slack.

vatsalm-scaleup

@vatsalm-scaleup

since my npm modules are namespaced @bit.collection.component, if I declare my module using only component name it does not work, any ideas on how I can make typescript type definitions work for my exported component ?

Josh Kuttler

@JoshK2

@vatsalm-scaleup you can include the d.ts file inside your component, it should work.
Can you share what you do when it doesn't work?

vatsalm-scaleup

@vatsalm-scaleup

what name i can give for my module declaration?

I am just trying to get rid of an error using very simple .d.ts file

declare module ‘component-name' {
const noTypesYet: any;
export default noTypesYet;
}

but it doesn’t reference to this definition file

Eddy Nguyen

@eddeee888

Hello! I'm having problem auto importing a React component in VSCode from a @bit package. It always come up as "No suggestions". However, after importing that package manually, any other autoimports in the file works... Has anyone encountered this problem before?

Screen Shot 2020-01-11 at 6.40.57 pm.png

In the picture above, I'm trying to import Button from a bit package that I picked @bit/semantic-org.semantic-ui-react.button. However, there's no option to do so

Screen Shot 2020-01-11 at 6.41.22 pm.png

In the second picture, after manually importing Button from the package, other components in the same package starts to come up ( ButtonOr, ButtonGroup , etc. )

Tally Barak

@Tallyb

@/all New beginnings. We are moving our community support to slack. We believe we can make conversations there more fruitful. Use this link https://join.slack.com/t/bit-dev-community/shared_invite/enQtNzM2NzQ3MTQzMTg3LWI2YmFmZjQwMTkxNmFmNTVkYzU2MGI2YjgwMmJlZDdkNWVhOGIzZDFlYjg4MGRmOTM4ODAxNTIxMTMwNWVhMzg to register to our community slack, if you are not yet there, and we will see you over there. Regards, the Bit team.

1 reply

Josh Kuttler

@JoshK2

Hey!
I just published a new version of React Native compiler and I would appreciate some feedback.
https://bit.dev/bit/envs/compilers/react-native/

Daniel Kappler

@nabbl

Can someone help me getting my stylesheets (scss) to work correctly? I want to do a separate component for them with namespace stylesand then refer to them in my other components. how do I make this work in angular environment ?

error: the component styles does not contain a main file.

Daniel Kappler

@nabbl

Why does it need a main file ?

ok.. just saw that slack is the thing now :D

Min Nam

@minnam

This message was deleted

Nikolai Iakovlev

@DeyLak

Hey!
I just tried to update my ts compiler and now I'm getting this error, when trying to build a component:

error: bit failed to build pik-pro.mobile-apps/pages/page-profile@1.9.13 with the following exception:
Cannot read property 'split' of undefined
TypeError: Cannot read property 'split' of undefined
    at getNameOfFile (/Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:301:56)
    at /Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:213:48
    at step (/Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:33:23)
    at Object.next (/Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:14:53)
    at /Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:4:12)
    at createConfigFile (/Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:209:12)
    at /Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:104:23
    at step (/Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:33:23)
    at Object.next (/Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:14:53)
    at /Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:4:12)
    at preCompile (/Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:100:12)
    at Object.<anonymous> (/Users/deylak/Desktop/ForLovelyMe/Repository/pik-pro-master-app/.git/bit/components/compilers/typescript/bit.envs/3.1.38/dist/ts-compiler/src/compile.js:73:32)

I used version 3.1.0 previously and it worked fine. Now I'm trying to update to ts@3.7.5 and all compiler versions with that release of typescript are throwing this error.

itay mendelawy

@itaymendel_twitter

Hi @DeyLak can you please open a github issue here https://github.com/teambit/envs ? Ill have my team look at it asap

Nikolai Iakovlev

@DeyLak

@itaymendel_twitter sure teambit/envs#86

Ryan Ju

@ryan-ju

Hi, I'm trying out the react-typescript compiler. The problem I have is that it puts the output from all components into a single top level dist/ directory, so everything is jumbled together. Is there a way to make it preserve the folder structure of each component?

My project structure:

├── package.json
├── src
│   ├── components
│   │   ├── SignIn
│   │   │   └── index.tsx
│   │   └── SignUp
│   │       └── index.tsx
│   └── utils
│       ├── auth
│       │   ├── jwt
│       │   │   └── index.ts
│       │   └── server
│       │       └── index.ts
│       ├── logging
│       │   └── index.ts
│       └── styles
│           └── README.md

dist/

├── dist
│   ├── README.md
│   ├── index.d.ts
│   ├── index.js
│   ├── index.md
│   ├── jwt
│   │   ├── index.d.ts
│   │   └── index.js
│   └── server
│       ├── index.d.ts
│       └── index.js

Ryan Ju

@ryan-ju

^ as you see, the index files from each component is put in the top level of dist/, so they overwrote each other

Josh Kuttler

@JoshK2

Hey @ryan-ju , I'll try to reproduce this error and see what is wrong.

Ryan Ju

@ryan-ju

Another problem,

$ bit import bit.envs/testers/jest
failed running npm install at /Users/ran/Projects/ui-platform-utils/envs/components/testers/jest
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@bit%2fbit.utils.validation.empty - Not found
npm ERR! 404
npm ERR! 404  '@bit/bit.utils.validation.empty@0.0.1' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'jest'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/ran/.npm/_logs/2020-02-06T10_50_53_789Z-debug.log

see troubleshooting at https://docs.bit.dev/docs/installing-components

run 'bit doctor' to get detailed workspace diagnosis and issue resolution.

Looks like the @bit%2fbit.utils.validation.empty isn't exported to npm?

Ryan Ju

@ryan-ju

I really like bit, but sorry I have to leave it, because I cannot get a MVP easily enough to convince my team to use it. Hope after a few years we'll come back when those issues are fixed.

Doron Tsur

@qballer

hey @ryan-ju are you around ?

I'm a senior developer on the team. Is there anything I can help you with ? I work mainly on the environment which compile and test code.

Anyways there was a move to a slack community. This meant that the team was mainly hanging there and we missed messages here.

I'm going to stay on gitter. Let me know when you get back.

itay mendelawy

@itaymendel_twitter

hi @ryan-ju i'm sorry for being un-responsive.
A while ago we've migrated the chat to Slack. Please join here to continue the conversation.

as for the npm i issue, you need to configure your .npmrc file to connect have your client configured to bit @bit registry. see here for more information.

Ryan Ju

@ryan-ju

Thanks for the response guys. Didn't mean to annoy anyone, it's just I'm under pressure to come up with a component management solution for my company. Currently we're deciding between Lerna and Bit, and I'm the one prototyping with bit. I'll come to the slack channel.

itay mendelawy

@itaymendel_twitter

no worries @ryan-ju . i completely understand tight schedules and I hope to be able to help you during the onboarding

Doron Tsur

@qballer

@itaymendel_twitter please ping me if you guys need anything

Joe Pea

@trusktr

Hello you all. Is bit good for managing a repo with a bunch of projects as git submodule inside the "umbrella repo"?

Joe Pea

@trusktr

I was trying a tool called Rush.js, which symlinks projects to each other all at once, so we don't have to run npm link in each of them for each dependency of each project. Does bit make developing (linking) with multiple projects easier?

Joe Pea

@trusktr

Looks like to use Bit, I need to buy into it's module specifier conventions. Can this be avoided? Suppose each project (which is a submodule in my umbrella repo) contains web components, and I want to share them across projects (some projects are apps, some are libs).

Does bit make it easy to use only Node.js-style import specifiers and store everything on NPMjs.com?

Ah, I see, Bit calls them "workspaces". So then, in my case, I am looking to have an "umbrella repo" with a bunch of Bit "workspaces" as git submodules. Would this work?

Basically, I'd like a big "umbrella repo" to house all my related apps and libs as git submodules.

It seems that we would need to run bit init in each workspace (git submodule). Now I'm wondering if this can be done automatically across all "workspaces".

Joe Pea

@trusktr

If I use my own server for hosting, is it possible to modify the @bit scope name to something else?

I'm gonna guess that any components published to a custom server are not discoverable bit.dev?

itay mendelawy

@itaymendel_twitter

hi @trusktr , we've moved to a slack community and left gitter a few weeks ago.
https://join.slack.com/t/bit-dev-community/shared_invite/enQtNzM2NzQ3MTQzMTg3LWI2YmFmZjQwMTkxNmFmNTVkYzU2MGI2YjgwMmJlZDdkNWVhOGIzZDFlYjg4MGRmOTM4ODAxNTIxMTMwNWVhMzg

As for your questions, BIt is designed to handle smaller components, and not for projects.
Usually, teams use lerna/rush to manage a small number of large projects in the same repository. On the other hand, Bit is designed to manage many small "projects" (modules/components) in the same workspace. technically it's possible to manage larger projects, but it is not optimized for it. Bit is optimized for projects with a relatively small amount of code and a lot of dependencies.
it's possible to group together several Bit workspaces, each with its own set of components, in the same "master" workspace.

as for sharing components to npmjs, it's possible, but you'll need to implement an extension to do just that. it's also possible to change the default @bit, but this is not supported when hosting code on bit.dev .

Joe Pea

@trusktr

@itaymendel_twitter Cool! Thanks for that info. Seems that Bit can be paired with Lerna/Rush. F.e. I can use Lerna to run test commands across multiple repos, and the test commands can trigger Bit commands in each of the projects.

What about symlinking dependencies for development? Suppose I want to edit code for a component and see the changes in multiple projects at once? Normally Lerna cross links dependencies, or we can manually link local projects into dependents the old npm link way, and test changes across them all at once. Does bit have such feature for developing a component and testing it across across multiple projects at once?

itay mendelawy

@itaymendel_twitter

this channel is no longer supported
we have moved to Slack
https://join.slack.com/t/bit-dev-community/shared_invite/enQtNzM2NzQ3MTQzMTg3LWI2YmFmZjQwMTkxNmFmNTVkYzU2MGI2YjgwMmJlZDdkNWVhOGIzZDFlYjg4MGRmOTM4ODAxNTIxMTMwNWVhMzg

mr.vacoo

@vacoo

djjd

Marc G.

@Mouvedia

compile() deprecated, please use compile() instead

that's a really cryptic error message to say the least

Where communities thrive

People

Repo info

Activity