You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be a very rare edge case, but I'd like to seet his fixed (a PR is on its way) and discuss this.
I have a react-styleguidist setup where I join multiple styleguides into one big styleguide. Each project (each individual style guide) uses babel and babel-plugin-direct-import. The problem is that when I build my big styleguide, babel does run from there and process.cwd() is not the root of every individual component anymore. This causes babel-plugin-direct-import not to find dependencies that are only used by individual components.
Long story short: process.cwd() not being the path of the module that uses babel-plugin-direct-import breaks it.
The text was updated successfully, but these errors were encountered:
Yeah, that would make the config syntax more complicated again and would require me to put the cwd into all .babelrc files.
The proposed PR doesn't require config changes. :-)
This might be a very rare edge case, but I'd like to seet his fixed (a PR is on its way) and discuss this.
I have a react-styleguidist setup where I join multiple styleguides into one big styleguide. Each project (each individual style guide) uses babel and babel-plugin-direct-import. The problem is that when I build my big styleguide, babel does run from there and
process.cwd()
is not the root of every individual component anymore. This causes babel-plugin-direct-import not to find dependencies that are only used by individual components.Long story short:
process.cwd()
not being the path of the module that uses babel-plugin-direct-import breaks it.The text was updated successfully, but these errors were encountered: