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
■ Could not read package.json: Error: ENOENT: no such file or directory, open '/Users/my-user/.configu/cache/packages/b11dbb3f9de1fd8f7f963b3b97e7cab3/package.json'
the folder "b11dbb3f9de1fd8f7f963b3b97e7cab3" is empty.
Expected Behavior
eval should work.
To Reproduce
No response
Context
configu store library changed its name to "configu-platform".
The text was updated successfully, but these errors were encountered:
I've looked into the issue and identified two separate problems:
Incorrect Store Type:
The configu login command generates a .configu file with an outdated store type. This happened because the library was renamed to "configu-platform", but the login command wasn’t updated accordingly.
Uninformative Error Message:
The CLI returns a vague error about a missing directory. This occurs because the underlying configu common package interface is trying to look up a non-existing store type, leading to a misleading error message.
Let's limit this issue to addressing the incorrect store type generated during login. I'll open a separate issue to improve the error messaging in the CLI.
Current Behavior
got an error:
the folder "b11dbb3f9de1fd8f7f963b3b97e7cab3" is empty.
Expected Behavior
eval should work.
To Reproduce
No response
Context
configu store library changed its name to "configu-platform".
The text was updated successfully, but these errors were encountered: