Yarn workspaces support

Bug Report

Describe the bug

Compilation fail when importing components from another yarn workspace.

To Reproduce

1. Create one docz workspace and one shared workspace
2. Create components on shared
3. Import them on docz
4. See error

Module parse failed: Unexpected token (11:2)
You may need an appropriate loader to handle this file type.
| 
| export default () => (
>   <Touchable onPress={() => alert('pressed')}>
|     <Text style={styles.text}>Shared Button</Text>
|   </Touchable>

 @ ./src/index.mdx 9:0-61 66:93-99
 @ ./.docz/app/imports.js
 @ ./.docz/app/index.jsx
 @ multi ../node_modules/docz-core/node_modules/babel-polyfill/lib/index.js ./.docz/app/index.jsx

Environment

• OS: macOS 10.14
• Node/npm version: Node 8.11.3 / npm 5.6

Additional context/Screenshots If I move the docz code to shared it will work. It only works if the components are in the same “project”. If you try to import from another workspace it fails.

If you setup docz in the root directory (outside all workspaces) it fails as well, but with another error.

doczrc.js

module.exports = {
  themeConfig: {
    colors: {
      primary: 'black',
    },
  },
  typescript: true,
}

docz package.json

{
  "name": "docz",
  "version": "0.0.1",
  "scripts": {
    "start": "docz dev",
    "build": "docz build"
  },
  "dependencies": {
    "shared": "0.0.1"
  },
  "devDependencies": {
    "docz": "^0.10.2"
  }
}

docz/src/index.mdx

---
name: Hello world
---

import Button from 'shared/src/components/common/Button.tsx'

# Hello world

<Button>Click</Button>

[aarshaw]

Ended up using something similar to this ^ …feels king of hacky but works

Updated doczrc.js to the following:

import path from 'path'

const modifyBundlerConfig = config => {
  config.module.rules[0].include.push(path.join(__dirname, '..', 'SHARED_PACKAGE_NAME'))

  return config
}

export default {
  modifyBundlerConfig,
}

[pedronauck]

For sure @brunolemos I agree with you that is related to docz instead of yarn. But, is not a “problem”, is an architecture decision. It’s not a good practice import from other packages in a monorepo without transpiling and since they will be in the node_modules they won’t be transpiled. What you can do in this case is change the loader do transpile from a specific node_modules since we’re ignoring all node_modules folder to be transpiled.

About create-react-app I saw this week on twitter that they’re dropping support for monorepo. So, I think that change the entire structure to support monorepo can be a good choice.