I suppose it makes it easier to at least click on the window below when all maximized 😬

If the marketplace just pulls the tarball (and extracts it) and does not try to install dependencies it actually should not have the same issues 😊

… a better way is to describe an installation process with something like pacote: just download and extract the extension which is fine for bundled extensions.

What do you think or am I just looking wrong at this?

…that method installs them even though the extension does not need it.

That is something worth to improve short term I suppose, mainly though better documentation?

The marketplace doesn’t have this issue because, if I’m correct,
It doesn’t actual install, it downloads an archive.

Perhaps…

It’s slightly nuanced I think. I totally agree on the separation, that would be a great dot on the horizon! Curious to see if you have a different vision here:

For self hosted the docs say to install extensions via “pnpm install <extension>”. If the extension has deps or even devDeps…

I found out that, in this case, Zod causes it. More specifically if an extension uses Zod. There is a deeper issue: extensions are not mindful about dependencies. Most don’t need runtime dependencies (bundler! 🥳). So (p)npm installing extensions is “dangerous” ☺️. I would love to see that improved!

Oh I tested this on NodeJS version 22 by the way!

If you are using zsh as your shell you can add a line to `~/.zshenv` to make sure it is loaded to all your zsh sessions, even the non-interactive ones like in your editor or IDE.

Put this in ~/.zshenv:

export NODE_OPTIONS="$NODE_OPTIONS --use-system-ca"

My current top three:

- Transparency overkill
- Border radius overkill
- Border radius inconsistency overkill

...that there are different radiuses for different applications! Even some Apple apps have a different radius... so that has not been applied universally meaning apps need to update that themselves. Thats going to take years. That is unfortunate imo... 🤷‍♀️

What it does:

• Syncs your entire project over SSH
• Skips heavy folders (node_modules, builds)
• Keeps .git history intact
• --dry-run previews changes first

Start coding on desktop, commit changes, then instantly pull everything to laptop and continue exactly where you left off! 🚀

Thanks!
I think I have upvoted the issues, I’ll check again later.

Thank you very much, appreciate this a lot!!

Ha! No worries! 😊

Hi @wordman.dev, have you had the time to try it? Just curious here 😅!

Congrats!

And SSE-C is supported by most S3 compatible providers and enables a bring-your-own-key for encryption needs.

On the email: you can override the default system email templates and that works pretty well but you can’t use translatable strings so it limits you to a single language.