@polotek @sue we’ll definitely dig in; I know folks who have gotten this running, let’s see if we can make it easy.
Conversation
Notices
-
Embed this notice
Anil Dash (anildash@me.dm)'s status on Friday, 05-Jul-2024 09:04:37 JST Anil Dash -
Embed this notice
Marco Rogers (polotek@social.polotek.net)'s status on Friday, 05-Jul-2024 09:04:48 JST Marco Rogers @sue if I run this locally with node 20, it works out of the box. It's probably a versioning thing with either node or npm. It's weird that it actually builds in glitch, but then just does the wrong thing somehow? Thanks for taking a look. To be clear, this is not important or urgent for me. Don't go out of your way on my account.
-
Embed this notice
Sue Smith (sue@glasgow.social)'s status on Friday, 05-Jul-2024 09:04:49 JST Sue Smith @polotek Shared this in the work slack in case anyone knows what's up with the vite build, I have ended up doing some weird things to interact with env vars in there though.. Perhaps you know this but we are doing infrastructure work to enable newer versions of node, quite a bit of that work still to come but we shall get there!
-
Embed this notice
Marco Rogers (polotek@social.polotek.net)'s status on Friday, 05-Jul-2024 09:04:58 JST Marco Rogers Instead of doing what I'm supposed to be doing, I decided to try to get phanpy running in glitch.
It doesn't quite work. Something is missing with the vite build setup. It doesn't output the environment variables.
FYI. There are some other warnings. The default build configuration seems to want node version 18+. But glitch is still stuck on node 16. That doesn't seem to stop it from building though.
-
Embed this notice