The idea here is to tell Vercel that use one specific subfolder of the monorepo for the deployment. Similar steps should be followed on other platforms like Netlify. We use Vercel at 64 Robots so I am going to focus on this platform for now. Tests are passing, we are ready to deploy. Adding the -directory setting we are telling Github that all the runs commands on that workflow have to be executed on that specific path.Adding the on.pull_request.paths setting we are telling Github that the action should be only executed when the PR contains, at least, one file on that specific path.Steps : - uses : name : Install dependencies ![]() On : pull_request : branches : paths : - 'workspace-a/**' defaults : run : working-directory : workspace -a github/workflows/tests-a.yml name : Tests Yarn is smart enough to not install twice repeated dependencies among projects.įor enabling workspaces you only have to create a package.json file in your repository root. ![]() It allows you to setup multiple packages in such a way that you only need to run yarn install once to install all of them in a single pass.Īwesome, so by default, we can have two projects and run yarn install on the root and yarn will take care of manage both project dependencies. Yarn WorkspacesĪ new way to set up your package architecture that’s available by default starting from Yarn 1.0. That way we could have shared components YAY! But, wait a moment, is that going to work just out of the box? Short answer: No. Last week we decided to merge those two projects into a unique monorepo. ![]() This also applies to the API endpoints and more stuff. So far so good but once the development is quite advanced we started to notice that there were components that had been used in both projects. One for the web made with Nuxt and the other for desktop made with Electron.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |