-
Notifications
You must be signed in to change notification settings - Fork 936
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vuejs relative path starting with @/ considered as packages #869
Comments
@idealley Thanks for reporting this. We are still in the process of finding a solution for absolute paths in require statements.
We are trying to find a good solution which will know to handle all the cases like the described here and in the following issues: |
I see! Thank you. I really look forward to it as this is for me the only blocking things to go ahead with Bit. |
Did you find any solution? |
Yes! We're going to provide an option to configure the alias ("@" in this case) in the bit.json file, and we'll use that configuration to correctly detect the dependencies. |
Yeah!!! thank you. |
Just to keep this post up to date, the feature is merged into master, and some e2e tests were added to make sure Vue files are supported. |
Thank you guys. Impressive work. I will try that in details. |
Expected Behavior
Imports other vue components or any other relative files when running
bit add ...
when the imports are structured as follow:@/
stands forsrc
orroot
kind of like in unixcd ~
it just replaces../../../helpers
and if you move files around the imports are not brokenActual Behavior
bit wants to resolve
@/components
as a node package and not as a relative path.Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: