Nx Office Hours: Building a Design System with Storybook

hello hello hello i gotta make sure my microphone is right so people can hear me so make sure hopefully i'm good and uh loud enough but we're back um welcome to another episode of phoenix office hours uh we talk about lots of cool things to talk about it goes with them we talk about other ecosystems and we have a special project today that we're going to talk about and how it integrates with nx you've seen me before brandon brandon t roberts on twitter and i have a special special all my guests are special but another special guest uh today and katarina why don't you go ahead and introduce yourself hi everyone um thank you brandon for having me i am a javascript engineer i work for narwhal and i also contribute to nx i am a google developer expert for angular web technologies in the google maps platform and lately i'm also doing some entrepreneurship with some friends and yeah and i also mentor women in tech yeah i've seen you yeah you've done definitely done a lot in the in the angular ecosystem and uh definitely do a lot of a lot of conference talks and things like i always really enjoy your talk so uh definitely good good stuff there and like i said the mentoring of girls in tech is definitely awesome there thank you so cool uh thanks to those people in the chat i see a few people in there that are chiming in already um like i said next office hours we'll we we take questions sometimes if we i'll go ahead and set up front if we we'll see how many if we get to questions or if we don't answer your questions now then we'll save them for later because we definitely want to make sure that we are listening to the community so uh but yeah on that on that note you can get into our topic for today which is if you've if you're watching this then you need you want to learn something about storybook and design systems and uh i'm going to learn some stuff too because i haven't done much with with storybook or design systems either so uh i'm looking to learn some some new some new tools today and catering is going to show and we can talk about how those things fit into the workflow and all that so yeah we can start with that um i guess what where do you want where do you want to start i'll let you you're you're this you're the star of the show yeah i guess um i guess potentially the most unknown word that some people may have i mean i guess that most people know what a design system is but let me explain what it is uh so our design system is basically the set of styles style rules design rules reusable components fonts colors that an application or an organization may use so if you have a site like for example the bbc the site of bbc i'm saying this example because i think there is an example on the storybook action on the actual storybook webpage that shows this you have like a website that has the news header and you have all the different buttons and the different avatars for the journalists for example or the different the specific style that a header or a quote or some things are displayed on the screen so all these rules that explain and describe how these things are supposed to be they're like the blueprint these are the design system this is what is called the design system so it's a so it's quite important for an organization a large organization or a large application to have a design system because it it really helps uh developers and so it sort of brings developers and designers together and it helps when you're stuck and you don't know what to use you have your design system and you sort of have like um a compass to guide you you know like this is how it's supposed to be and i have to go pick these things from these components and put them here so it's like it makes things easier yeah i remember at a previous uh job that we where we i guess we more or less called it a style guide but it was more like a like a design system also where he had all your like you said your components or your things laid out that you wanted to use because of course if you're building like multiple applications and things you want them to have some level of consistency and uh like a similar look and feel across different products right yeah definitely so in in a past company i was working for um so the usual thing is and that was the case for the past company i was working for it was like you have the designers and they give you a link for figma for example or for invisio or some or something that you can that this uh this tools sort of have css integrations and you can actually copy the the css that they they sort of spit out right and sort of you have this figma project or this envision app that you can zoom in and zoom out and see uh this thing here and this in there and how it should work and you sort of copy and paste from there and you try to imitate that with your code um but and these are or go ahead no no please say i was gonna say and these are um they're not just like most and most of the time these are like i call them living examples but they're actual pieces of code that you are there a piece of code that acts should actually work when you when you use them right they're not just like mock-ups and no no they're not they're not like mock-ups you can click them and go from one place to the other place so these things are yeah are very very helpful and storybook takes these things one step further because you have this this uh you have these um yeah the figment whatever the designers make you have this as a guide and when you you create them into components and you create them into actual code and you turn them into actual components made from code then storybook actually gives you the ability to browse these components live like as you're browsing figma for example you will now be browsing the actual code that you wrote or another developer wrote and see how the actual code works right because with figma you see how it's supposed to work but we started we see how it actually works because you're actually viewing the actual component um so how does it do that uh storybook uh i let me read the the definition on the site like the elevator page is uh storybook is an open source tool for building ui components and pages in isolation so what this means is that when you have for example another an angular application or a react application you have organized in components uh when you install storybook in that application you go in your component folder for example and you can create a file that is called for if my component is called katarina.component.ts my story file will be called katarina.stories.com yes for example and in there you can actually import the component that you wrote and write some scenarios for it it sounds like an e3 test i guess for you for someone who hasn't used it sounds like an it's a test and it certainly does look like that because you import the actual component and you write some scenarios for it and then you can uh start storybook you can run storybook and it's a it fires up a local server where it just serves that component which is pretty amazing because you do not have like to to start like a complex stack and do a complex navigation to to this page to trigger the specific state of this button or this toggle that you need you can just write that i want this toggle to be on and just fire it up and seats you know what i mean yeah yeah that yeah that's definitely something that i uh always uh that i've liked about you know storybook and the systems like that is that you the biggest part is that you don't have to fire up an entire development stack to to like work on one component because yeah if you have like a large system or you know a large set of systems that may be using that then like i said having to bring up all that infrastructure or if you're maybe application like say that's pretty big um and you need you like say you have to click around to get to a particular area just to look at that one thing as opposed to bringing up a separate ui and being able to build out those uh components faster that way it definitely definitely helps with like your development turnaround yeah and it also helps because if you also have like a large application as you said you don't have to sort of navigate to that specific place and actually trigger the state that you want to test you can just write this story that will make make the component look as you expect it to look so yeah that's that's that was that's what storybook is yeah look and like i said i i've looked at storybook uh in the past and i've used something similar that was like a i said building something in isolation for components but storybook has definitely grown a lot and likes it up as we can see on the site it has support for multiple frameworks and different ecosystems which is which is good that they support those um so yeah that uh at least that's just a good intro for uh storybook as far did you have anything else you wanted to add as far as store book in general nope that's it i mean it does more things but yeah i mean that's the the essence all right okay okay so we talked about uh like in general what a design system is and the um like what storybook does in general um i had brought up the because i did want to look at this one the like as you mentioned before yeah exactly uh bbc storybook uh so they definitely have a good suite of components and things that they can show you uh what those look like just by clicking through there and uh and you can actually change the colors and change the fonts and everything okay so yeah i'm just gonna do some fiddling here yeah okay yeah that's definitely definitely pretty cool so um but yeah i'm sure theirs is uh fully fully fleshed out and they've kind of iterated on this for a while and like this powers their uh powers their site and everything so definitely some cool stuff there um so yeah so we have we have the we have the design system out there we have storybook um so how do we're going to talk about like bringing those two things together with uh nx itself yep so if you in in the starbucks website i'll i'll find the link they have a pretty great um guide of how to build the design system with storybook and as you're reading this guys you're thinking or i was thinking that or we are wrong that nx will definitely make this much much easier to do uh because um when you're building a design system for example you have to you have to think of all sorts of things you have to to organize your code you have to to think of how to break up your code in smaller components of how to to keep things organized of think of the architecture of thinking of reducing reusability of course um so all these things nx helps you definitely with all these things because um with nx of course you you can start developing in a monorepo and an ex sort um and start and the design system would be benefited from that because you would have your applications and then you would have your libraries that would be split up for example in presentational components and this this that would impose uh a much much more efficient way to develop your design system for example um also uh nx helps a lot with uh with streamlining the whole process like with the testing and the building and uh integrating with the ci so the interest because the interesting thing about storybook is that as you saw you can not only can you build it and not only can you you fire it up locally and test it you can also actually build it and deploy it and and have it presentable like we saw with the bbc case um and what's also great is that nx integrates with storybook and the cool thing is that it actually generates stories for you so if you have some components ready you don't if you already have your design system ready for example and you have some components ready you don't even have to write code you just you you just start a net you just install an x and an x will generate stories for you using the storybook package it will analyze your components and it will analyze the inputs or the props for example for for react and it will generate some stories for you that you can instantly use and what it will also do because mx integrates with cyprus and sc and storybook works with cyprus too jenner um nx will generate end-to-end tests that will use cyprus and cyprus in cyprus you don't even have to write new scenarios you can just import stories and just fire up these stories and cyprus will test the stories without you needing to write new e3 tests which is also cool i think because you can actually reuse the the the work that you have already done yeah that is that is very cool it's like that like you said it's you essentially get a complete system out of like from head to hand not that in the end but uh you get a complete system there as far as like you said being able to build the components like uh just by themselves and being able to see how they function see what the input and office are props and then it's like you said you can go take it to the next step as far as being able to test those um test those using like end-to-end tests um to definitely a lot of flexibility there i'm not sure if this was the link you were mentioning before yes okay design systems for developers yeah so they even have yeah some of this they have where they walk you through how to put the design system together uh but like you said if you're working with nx mono repos then you you get a lot of these uh like a lot of the setup and uh generation parts out of the box there so uh i did place a link to the chat for the in the chat for those to go and uh read the post by katerina also that talks about what we're gonna uh some of the things we're gonna cover here as far as building your own design system there so yeah like i said that post is there we just published it look at this last week um so definitely check that post out and uh we'll link to that post in the show notes uh there um so yeah those are there any other like i would like to talk about like some of the pieces that you mentioned before about how um like how does building your component like building your components in smaller libraries and uh and that like factor into how your how your design system works like you said you want to how do is there is that something that you're like optimizing for that helps with your uh design system or your storybook setup also is just having smaller components um it's not really smaller components per se but if you so the first thing i i would do if someone would ask me to if someone would show me some mock-ups for example and would tell me um let's make this into an application i would try to think how to break this down into into smaller parts like for example in this page here we try to identify that okay we have a logo on the top left we have a menu uh the menu items are all the same we have a title we have a button we have different states of the bottom we have some chips down on the bot down at the bottom right we have an image um so i would try to to think of all these different things that there are there and try to think how i could break them up into components and break them down break them down break them down and how i think there is also a rule my rule of thumb mentioned in this post or and maybe i've read it somewhere else that if there's a component a part of a visual parts that you use more than two or three times then it's worth making it into a reusable component for example i remember it was two or three years ago that i was doing an interview for sky scanner and they had this uh the task that the take-home exercise for the interview uh they gave you this ui that you had to build right and one of the comments that i got but and they sort of said that we're looking at a component-based architecture and one of the comments that i got back was that you could break this even more down to more components and i always think back to that comment from that interview by the way i was not hired for school okay i worked i think it worked that worked out better for us so yeah so yeah i always remember that and um yeah and the the great thing about the library is that you can use in nx because so in the next you have a monorepo so it works pretty well if you have different libraries so this enables you to have a library for example that is just presentational components like no logic and it's just ui components and then you can put all the logic and other components and then you can bring all this together and import them in an application so this is uh yeah this is how it helps if this answers your question yeah yeah definitely so and like i said i i also like uh breaking components down if yeah if i if i see a a component with a lot of pieces in it then i also take a look at um i also take a look at trying to break it down into smaller pieces so that um they maybe can be reused or like you said maybe it turns into like a shared library of components or things like that so definitely um definitely agree with with what you said there [Music] uh let's see well i see a couple people have some questions and we'll we'll we'll get we'll look at those questions when we get there um [Music] so i guess where do we want to go next do you want to like show walk through how we go through setup uh yeah sure sure so let me share my screen and let's and let's hope that there is not a very great lag yeah well we'll work we'll work with it either way because i think some some good good content in here so yeah so first of all i'm going to show to i have recorded the part of creating an x workspace and london storybook because i guess most of you of the viewers i guess if you're at an ex-office hours you have used the next so yeah we got some yeah i'm pretty sure we got some regulars some regulars in here and maybe some new people that are looking to add their own design system so maybe there's a mix i'm sure the chat will will let us know either way cool but if you're ready for me to add your screen just uh just yes i am ready you can add my screen okay there we go can you see it yes wow that was fast okay so let's see so yeah this uh this is the video where you just type npx create the next workspace and then the name of your the monorepo and it will create an nx workspace so now you have to to to choose which application to start with in your workspace and we will choose react for this example and you give the application a name and you choose the the default style format so um storybook suggests to use style components for a design system because it keeps all the style it keeps everything like in a single file and everything in a single place and it works better for design systems i have not used style components much sorry so so for this example i think i chose css yeah so usually i choose yes use an xcloud i said no no so yes it will install everything and the the after afterwards the workspace will be ready and then all you have to do is type uh yarn add narwhals the narwhal storybook package which is that norvel slash storybook and this package contains all the scripts that you need that nx needs in order to generate stories for you and generate storybook configuration for you and also my uh some migrations that i didn't talk about but maybe we will talk about later so blah blah blah it's uh it installs the storybook so let's go the storybook package works for uh react and angular correct reactant angular we have um so the thing is that for react and angular we have a code generators but the narwhal storybook package does support other storybook renderers as well so if you do the manual work because it was recent actually it was recently uh added to to work that way i think if you do the manual work of generate of creating stories and writing stories and writing config server configurations on your own and then you just want to to serve the storybook and build storybook and uh serve build tests and whatever then narwhal supports that nx supports that if you use html for example or is valte but it will not do the work of actually doing the code generation part uh i see yeah yeah that's the catch potentially someday yeah i would say we can definitely um i know we have uh plug-ins for vue and svelt and other ecosystems so that i'm sure if if if we don't if those plug-ins don't support it yet then they're probably probably working on it at some point so but we know that we know the the option is there to use it yeah so now we installed the narwhal storybook package and i went after this i went into the trouble of generating a library a ui library and adding storybook to it but we will do it as well manually so that you can see it but now for example initially i had created the ui library and i had the react component here and i clicked the annex generator the the storybook generator and it generated automatically um this story but let's see how you can do it on your own um i can use nx console to show you nx console is the gotta get that nx console plug in there yeah if you're not using if you're not using uh if you're using vs code and you're not using nx console you need to go ahead and go to the extensions and and hit that hit that install button for index console there so you can you can get generate these things even quicker so let's generate a react application a library sorry react library let's give it the name katarina because i cannot think of another name now oops friends we want anything else no and run and now we have the new katarina library and that's what you is that what you uh use when you're like demoing things you got the the katarina component the katarina library and everything i see i see where it's going another thing i do is uh when i write console logs in like for example i work now for a client and there's a code base that is used by hundreds of developers whenever i write a console log i start the log message with katarina so that afterwards i search katarina and in case i have forgotten any console logs okay yeah that's a good tip about it i didn't even think to do that i might i might have to use that one too so now we have a library generated by an x just a normal library with a normal component um and now i can go to the nx console and actually let me add a property actually no i'm not at the prop and if i go to to the nx console i see that i have the normal react storybook configuration which set up storybook for react library and if i click this um the library was called yes and i say i want to configure cypress generate cyber specs that will automatically generate spec files in a cyber c2 app and it will generate stories files and they run it then you will see that in here it added a storybook folder which has some configurations for storybook which are default for everything and some webpack configuration and some cs config configuration and then it also created the katarina story file and now i can go and if i go now and run storybook see now he's showing you showing me more tips here just running things directly from the directly from the internet i'm up here running all these things manually [Laughter] well [Music] like i said i'm i'm i'm learning some learning some new new things here so uh some good tips so now here is my here is my component which i in i'm i put from here the catherine come on welcome to katarina and here it is if i had some props they would appear here and i could edit them and like we saw with the caller in the bbc example so that's it as you saw it's very very simple you just click a button and say generate storybook configuration and it will just generate the stories for you okay so is this something that you like can continually have to do uh let's say if you update i don't know if you're if you're gonna excuse me go to that next but if you have if you would have added props or if you go like let's say you update your component does it support uh those things also yes so if i have of course if i update my component and i add a prop here and like this right yes i think okay this is welcome to an x okay now there is an error no no props should it be prop style oh sorry a long time since i patched react sorry no problem okay there we go uh yeah i don't know what oh okay yeah now it's wrong because it sees that here we have some props so you go to an x and i hope this works uh it if you generate stories for caterina i think it will regenerate everything let's see yes yes so it fixed it you see okay cool so now we can run again is it still running no it's not running still not missing so now if i go and run again [Music] so yeah if you update everything there is the other schematic which is simpler it will not generate the whole configuration it will just go and generate stories for the new components or for the components that have been affected for you okay so so even if you have some that's another good thing there even if you have some components that you haven't changed then you run that again then it'll just leave those as they were right i want to say yes okay i'm gonna go with yes i'm going to go with you but i'm not sure sorry i maybe maybe not [Music] i'm sure yuri is watching this and pulling his hair you're yuri i'm sure he's doing fine if he's in the chat he'll he'll uh chime in and then we can we can put his we can put his comment up here if so but uh but yeah yeah and of course it's not showing something now because i should have put something in the boolean there but yes you see the toggle here that is just a boolean and you see that the story is updated so yeah so yeah that's pretty much it so you see how how simple it is and with if you're also using the nx console you don't even have to type the commands you just just a click of a button right so it's pretty cool yeah it's definitely cool um and you didn't have to like i said you wired all that up just by like you didn't you didn't have to type much besides uh of course the the the katarina libraries and things yeah but uh but yeah you only had to type that a few commands and were able to get that entire uh stack up there except with that integration there so definitely cool stuff there yes um no no go ahead and i'll go to the migrations afterwards yeah that's all i'm just going to ask uh so that's kind of like the workflow right you you work on your components you regenerate your stories and uh then you kind of tweak your tweak your components to get them like in a place where you're ready to drop them in the application yep cool so yeah and then you just uh and yeah you have your components you have everything and then you fire up storybook and you just have uh you just see the the components of a certain library just appear in in storybook if i had more components here they would appear underneath here like we saw in the bbc example what's interesting is that storybook has this feature called starbuck configuration where you can it's like i think it's it's like a little bit like run many or i don't know so you can run um that you have a configuration file that you have to manually create on your own nx does not create that for you you can create this configuration file and you can add different ports for different storybooks so if you have multiple libraries like here we have the ui library in the katarina library we can say that katarina will run in 4 4400 and ui will run in 4500 or i don't know where and you can fire up storybook and it will show the different storybooks under the same thing here because yeah here we only see from one library but with storybook composition we can show more than one libraries or more than one storybooks at one time okay yeah excuse me we got a question here is there a way to have one storybook for a monorepo project with multiple libraries yes so the answer is no because each library so each application each project needs its own storybook because as you see here we have one root storybook folder where we can add some general settings but and some general settings for webpack for ts config but each library has its own store book configuration and its project where uh the root one is imported and if you don't want anything specific you just don't add it you just skip the defaults but with storybook composition that i said you can create i think in the root folder or somewhere this configuration file that will enable you to run all the different story books and show them under one place yeah but you will have to have one specific storybook for each one of your projects i see um yeah so i think that yeah enter yeah well i don't think that was a good answer to that question and i think you had pretty much covered that one uh and this can i roll back if the executed man if i execute the command with the wrong configurations um yes i think this is more um uh like it's more of a source control question if someone generated the storybook and they didn't put the right maybe they didn't put the right project in or something like that but you could easily i believe you could pretty much do that with um just rolling back the changes in your repository and then just re-running them re-running them again with with uh nx console because it saves you time you gotta um so yeah the the in that the the post that you wrote was using i believe you used to react in the in the post that you wrote for the blog right yep yeah so um so there was a question um would you leverage other tools to build design systems for like for react-based systems how easier tailwind or shocker ui as libraries to build reusable design system elements i haven't used this i haven't used tailwind or the other tools so i couldn't really say yeah but i guess the answer is that whatever works best for you so if you have experience with tailwind i guess that this would be the easiest way or the fastest way for you to go but as you saw next has a lot of things going for it so i don't know yeah but i think like you like you mentioned before even you used uh you just used css uh instead of style components for you yeah for your example right so i would i would think that you would be able to uh use that or use other you know patterns or libraries for your components and still have them pretty much work maybe maybe it'll take a little more integration there but i think that that though i don't see why that wouldn't be something that you yeah i mean an ex support system as you saw an x supports all different types of styles right yeah they're definitely there are definitely many ways you can style things and react out of the box i will say i will say that um and even even in angular 2 there you can there are multiple ways that you can style your components whether you're just like using the built-in approach or tailwind or something like that so um definitely some options there um yeah you said that like you have your initial your initial set up for a storybook and then you can generate your stories and let's like i think we're kind of going through this now where you can uh you're on one version of storybook and uh you mentioned something about migrations and how you can maybe move from one version to the next or i guess how does how does that work so uh very good question so if you go to the nx console you can you browse you can see um that you have storybook migrate defaults five to six so uh storybook uh when it went from version 5.3 to version six they did a major change they changed uh they basically did a breaking change where they changed the the files that are added in the dot storybook folder they changed the names and the contents of these files so if you have a large uh if you have a large organization a large application you may have hundreds of libraries and hundreds of storybook folders so we wrote a schematic a generator that will check the version of storybook that you have and it will actually go through all of your libraries and generate the new configuration the storybook 6 configuration for you and it will put the old configuration into uh an underscore old folder because you may have some custom configurations there that you may want to copy uh so this this is what the migrator will do and it will also update all the packages to to the versions that they need to be so yeah that's it it saves you a lot of work because usually we do not usually um there aren't many changes that you do to the default configuration so it's so it's pretty handy and now it's i think it's landing in the next version or you know i know it's ready and it's sort of merged already we have a new migrator that will migrate your store your angular stories to to storybook 6.2 because there was another breaking change or i think just change that will be deprecated after version seven i think that uh changed some syntax of the actual stories uh so we went into so this uh this new schematic will go we'll find all of your angular stories and it will fix the syntax for you so it will actually do the code changes that you would have to do manually to go to version 6.2 which is yeah yeah it's pretty handy again very cool definitely some some good work uh you all are doing in the the storybook uh package there because like i said going from i remember the going from version five to version six was like say a pretty big uh feat in itself uh even just the changes that they made and trying to adapt yeah uh like existing workspaces to to be able to let them migrate to the latest version at the time also so definitely definitely good there uh phillip chimed in on the you can have a shared storybook instance uh you still need storybook config for each individual library but you can have a config that renders them all another yeah i think that goes along with uh what you mentioned earlier about even if you have the the different storybooks on uh individual ports you can combine them all together um into one as far as displaying them um so yeah definitely good one there this was a good a good question i don't know if you saw any did you see any questions in the chat that um were uh look at is my screen still being shared no yeah i can i can still see your screen no no yeah let's let's unshare my screen okay here we go thank you let me look at the chat yeah i had to let me put stream yard in my other monitor yeah i'll bring up one here and then uh then if we we'll try to do this one and then i think we'll i think we'll be about good for for this one uh this is it should we write all the business logic like fetching and all the implementation in a component to work with storybook um and i think that goes along with writing your components in isolation but um i don't think that you would have to do you don't you don't have to do anything specific with your components for a storybook right yep exactly and yeah just how it is and you don't have to do anything else yeah so yeah you can build build your components the same way you would build them if you didn't have storybook and then like it like said it's an additional layer uh you can have there to to kind of build them in isolation so you're not having to build them inside the app yeah and maybe the question means that if you have like um if a component fetches some data from a remote place or i don't know what then what would happen would this uh would you have to fire up the uh a server as well or anything but i guess i think i'm pretty sure that in a storybook you could actually mark the data that you want so because it does sort of work like like an e2 test right so if you you wouldn't have to fire up your your server your remote server or anything you could just write some mock data that that this component could use in order to display what you want yeah okay maybe no that may i mean that makes sense to me like i said even i would say if you're building some of those components that way then maybe they should be a little more um isolated from like http interactions and things like that but if those ones are just like reusable ones that would be a good way to keep those then that the way you can just drive them from the storybook instance itself and like tweak the values uh and things that go in there uh so yeah that i think that is i didn't see any additional questions in the chat room so uh i think that's a good place to call it there we can start getting these get these additional i get these additional plugs in here so i'm going to bring the the uh i'm gonna bring the the share back up here um we already talked about and one thing we didn't mention is that storybook is built uh with nx which was a good uh collaboration had there so we recommend using storybook in your applications and then in turn we worked with the storybook uh people um about integrating nx into their workflow because they saw we saw the val saw the value in both in both areas so definitely some cool stuff there so if you want to contribute the storybook you can check out there get a project and uh of course give them a star give nx go to nx.dev take a look at our docs and we just learn more about how to use a storybook and build your own design systems because as we mentioned if you're working in a monorepo and you have multiple applications and you want to have some have a better consistency there and share components and be able to build those things in isolation definitely use uh to check out nx uh for that uh let's see got the other so i gotta get banners up here um uh follow nxdevtools on twitter i'm going to remove this share here follow nxdevtools on twitter uh we all we are we have we look at those when people ping us there and try to answer your questions um you definitely go let's say go to nx.dev and check out our nx community page uh where you can join our slack uh workspace and get support for if you have other questions about storybook and we have narwhalians that hang out in there too to help out with that uh i think i already threw my handle up here but there it is brandon t roberts on twitter and katarina is cyber city is that did i say that right yes cool uh definitely give her a follow on twitter also uh so definitely some some fun to be had there uh so yeah if you're interested in contributing to nx you can go to github.com and we have uh guides there that show you how to contribute to the repo and help build this open source build framework that we're never on so yeah with that i think we're we're good i'm gonna get this one off of here uh katarina thank you once again for coming on uh nx office hours like i said we we talked about we wanted to keep things casual so i hope uh hope we we we kept things pretty casual as far as conversation goes so hopefully we'll hopefully you'll come back on again another time and we can chat up some more about uh some other things other cool stuff that you're doing because definitely doing a lot of that sure great thank you for having me it was great fun yeah sure uh and on that i think we'll call it so thanks to everyone in the chat uh we will see you in a couple of weeks on the next session of nx office hours thanks see ya bye

Channel: Nrwl - Narwhal Technologies Inc.

Views: 1,408

Rating: 5 out of 5

Keywords:

Id: FuqiYoqDbbw

Length: 50min 22sec (3022 seconds)

Published: Mon Jun 14 2021