title: Symlinking in monorepo - using lerna
body: <p>I am creating a monorepo component library with react, <a href="https://lernajs.io/" rel="nofollow noreferrer">lerna</a> and <a href="https://storybook.js.org/" rel="nofollow noreferrer">storybook</a> to display my components. Each component gets its own package. This way I can import components to multiple projects with out needing the entire User Interface. The main issue that I am facing has to do with symlinking packages. </p>
  
  <p><strong>Example:</strong> </p>
  
  <p>I have a Button component/package and a SlideoutMenu component both are unpublished. For display purposes in storybook/development. I would like to import the Button into the SlideoutMenu's story. So that I can use it to trigger the menu. Basically this is a dev dependency. It is not to be included in the build of the SlideoutMenu. </p>
  
  <p>How do I link this type of dependency?</p>
  
  <p>I have tried symlinking them using npm link which works locally but if I push the branch to github, at least currently the symlink is lost when a co-worker pulls the repository which obviously not ideal. Not really sure how to get symlinks to work with git/github</p>
  
  <p>I have also tried to add the dependency like so inside SlideoutMenu's <code>package.json</code></p>
  
  <pre><code>devDependencies: {
    "ui-button": "^0",
  }
  </code></pre>
  
  <p>this works to import but if I update the <code>ui-button</code> components background color for instance. The <code>ui-button</code> dependency inside SlideoutMenu component will not be updated I tried running <code>lerna bootstrap</code> after making this update but it doesn't seem to update the installed package inside SlideoutMenu.</p>
  
  <p>I would love some input on how to manage a monorepos dependencies and dev dependencies using symlinking and available to co-workers when pulling the repo from github.</p>