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
On this day in 2024, I also ran into this issue. I suspect the problem is caused by Volta, but I still want to use Volta. My temporary solution is to manually modify the symlink. Here, I’ll use the scenario where npm install --global alfred-npms doesn’t work as an example.
After running npm install --global alfred-npms, a symlink for alfred-npms is created in the Alfred.alfredpreferences/workflows directory. However, the symlink points to an incorrect location, which doesn’t exist. The actual installation location of alfred-npms is /Users/xxx/.volta/tools/image/packages/alfred-npms/lib/node_modules/alfred-npms. So, you just need to manually adjust the symlink to temporarily resolve the issue.
Here are the steps to resolve the issue:
Navigate to the Alfred.alfredpreferences/workflows directory and delete the incorrect symlink using: rm alfred-npms
Create a new symlink pointing to the correct location: ln -s /Users/xxx/.volta/tools/image/packages/alfred-npms/lib/node_modules/alfred-npms alfred-npms
Go back to the Alfred workflows, and you should now see the alfred-npms workflow available.
It looks like Volta uses a temporary path when executing, we could tweak aflred-link for Volta, but not sure if it's worth it as Volta could change in this regard at any time.
For detailed information, please refer to: bchatard/alfred-jetbrains#276
The text was updated successfully, but these errors were encountered: