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
A user from Gitter encountered this issue when importing a component. Bit throws the error above.
Steps to Reproduce
create a file 'src/index.js'.
create another file 'src/bar/foo.js' with the content require('..');.
bit add src
edit bit.json file and add "resolveModules": { "modulesDirectories": ["src"] }
tag, export, and import to another workspace.
the following error is thrown
unable to add the file "components/src", because another file "components/src/package.json" is going to be written.
one of them is a directory of the other one, and is not possible to have them both
Expected Behavior
Should import with no errors
Specifications
Bit version: 14.1.3
Node version:
npm / yarn version:
Platform:
Bit compiler (include version):
Bit tester (include version):
The text was updated successfully, but these errors were encountered:
…hs, also, avoid assuming that custom-resolve was used only based on the relative-path and the existence of the config. instead, explicitly mark custom-resolved as such.
…tom-resolved used (#105)
* fixteambit/bit#1734, recognize "." and ".." partials as relative paths
* avoid assuming that custom-resolve was used only based on the relative-path and the existence of the config. instead, explicitly mark custom-resolved as such.
* bump version
…odule-resolved incorrectly (#1735)
* fix#1734 from bit-javascript, avoid identify "." or ".." as custom-module-resolved incorrectly
* generate links correctly for components that have the invalid custom-resolve saved
* bump version
Describe the bug
A user from Gitter encountered this issue when importing a component. Bit throws the error above.
Steps to Reproduce
require('..');
.bit add src
bit.json
file and add"resolveModules": { "modulesDirectories": ["src"] }
the following error is thrown
Expected Behavior
Should import with no errors
Specifications
The text was updated successfully, but these errors were encountered: