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
When the cache location for pub is different from $HOME/.pub-cache, the bootstrap command fails to generate IntelliJ files.
Using a custom cache location is needed for example on a GitLab CI, which does not allow to use built-in caching (to speed up the CI) outside of the project directory.
Steps to reproduce
Define the PUB_CACHE env variable to a custom location (for example in your project): export PUB_CACHE=myproject/.pub-cache
Activate melos: dart pub global activate melos
Add melos to the PATH : export PATH="$PATH:$PUB_CACHE/bin"
Bootstrap your project: melos bootstrap
Melos successfully download packages but fails at generating IntelliJ files:
I expect melos to follow the PUB_CACHE location to create the IntelliJ files.
Screenshots
No response
Additional context and comments
Disabling the IntelliJ files generation in the melos.yaml config file allows to fix the issue, but it is not the best solution as I use them for Android Studio.
My current fix: modifying the melos.yaml config directly in the CI to prevent IntelliJ files generation:
Is there an existing issue for this?
Version
6.1.0
Description
When the cache location for pub is different from
$HOME/.pub-cache
, the bootstrap command fails to generate IntelliJ files.Using a custom cache location is needed for example on a GitLab CI, which does not allow to use built-in caching (to speed up the CI) outside of the project directory.
Steps to reproduce
PUB_CACHE
env variable to a custom location (for example in your project):export PUB_CACHE=myproject/.pub-cache
dart pub global activate melos
export PATH="$PATH:$PUB_CACHE/bin"
melos bootstrap
Expected behavior
I expect melos to follow the
PUB_CACHE
location to create the IntelliJ files.Screenshots
No response
Additional context and comments
Disabling the IntelliJ files generation in the
melos.yaml
config file allows to fix the issue, but it is not the best solution as I use them for Android Studio.My current fix: modifying the
melos.yaml
config directly in the CI to prevent IntelliJ files generation:The text was updated successfully, but these errors were encountered: