spicemix

I see this may at some level be an argument between nvm and homebrew. In which case, really, you just need to make nvm work with homebrew. Brewfile installs etc...

OK I commented out the nvm.sh line from my zshrc and rebooted and did as you directed. Interestingly, the place it hangs is on the `manpath` command 80% of the...

You might not be giving me enough directions. I just get an echo back of a path: ``` %time nvm_change_path /usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/[me]/Library/Android/sdk/platform-tools /bin /Users/[me]/.nvm/versions/node/v16.14.0 /Users/[me]/.nvm/versions/node/v16.14.0/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/[me]/Library/Android/sdk/platform-tools ``` If I just run `time`...

OK I did ``` % nvm unalias default % nvm use system ``` Rebooted, everything worked fine and fast, until I ``` % nvm use stable ``` Which is still...

Can I defeat the manpath change? Because I'm 99% sure that is what's doing it. My system isn't extraordinary for a dev machine.

OK! So it appears adding this line to ~/.zshrc above the nvm lines works around the problem for now: ```sh alias manpath=false ``` I believe the Chrome beachball I was...

Thanks @YOU54F nice response though after I filed this I had enough trouble getting all of these things working I bailed for the time being. If I get back into...

> Just out of curiosity: > The reason I ditched _Hammer.JS_ and used above approach was a terrible conflict with Chrome's devtool device/touch emulator. > Essentially, when assigning new 'Recognizers',...

Looks like a module loading/resolution issue...Lame is back on CommonJS and Angular is well into ES Modules. I see Lame is fully included in the webpack bundle, but it isn't...

OK here's a kludge that worked for me just now with Angular 13. Using `await import` in an IIAFE: ```typescript let lamejs: any; (async () => { lamejs = await...