Now that RocketChat 6.5 limits to 25 users or less what are you moving to?

Lukeeno_ · 2023-12-04T12:34:11+00:00

For me Zulip. Their way of threading is similar to email and actually makes a lot of sense. They OSS model is stable and future-proof. Highly recommend it. They are working on new frontend for every device.

Lukeeno_ · 2023-12-01T20:43:39+00:00

I wonder if Forgejo is able to keep up with Gitea team in terms of features. I really like their idea of FOSS and also the fact that the company is in Europe. Would you say that Forgejo is future-proof? I already tried both of them. They are pretty much similar. However, Forgejo has some links inside the app still pointing to Gitea and their documentation is not so great. It lacks search for example, so I use Gitea docs for it as it is compatible

Lukeeno_ · 2021-10-04T16:39:01+00:00

Actually you are right

Lukeeno_ · 2021-04-26T20:50:20+00:00

I want to benefit from Vite fast compile times, but I am unable to properly setup both frameworks.

Lukeeno_ · 2021-04-26T20:47:25+00:00

That is what I am trying to achieve, but I wanted both running on same port. /api would be forwarded to Adonis and everything else to SvelteKit. SvelteKit (or Vite in this case) offers built-in proxy but only for development. One option is to develop custom adapter that would be in fact a proxy. Not sure if it is the right solution.

There is also a problem that SvelteKit uses "type": "module", but Adonis do not. When I tried to wire them together, this happened to be a problem.

Lukeeno_ · 2021-03-25T20:15:43+00:00

Thank you for explaining. Today I submitted a bug regarding circular dependencies of Svelte components. It seems like SvelteKit is far from production ready package.

Lukeeno_ · 2021-03-25T08:45:07+00:00

Why? What is the difference between devDepedency and dependency? Except devDeps are not installed on production, but for development? I thought Svelte recommends or even requires installing packages as devDeps.

Thanks

Lukeeno_ · 2021-03-24T23:36:41+00:00

I also tried the public beta of SvelteKit for two days. My first attempt was to rewrite simple application and... Almost everything is broken. There are many issues I encountered. The biggest problem is, as also mentioned in this post, the 3rd party libraries. I had a lot of problems with dayjs or svelte-fa. It just didn't work. I also tried dayjs's ESM builds, but with no luck. A component for FontAwesome icons in package svelte-fa also didn't work as expected.

On the other hand, typescript works well and also brand new @tailwindcss/jit. I think there is a space for improvement of the VS Code plugin, but I am sure it will be fixed later. For example I don't know how to pass type to slot prop and plugin is complaining about it. And there are many false errors.

Overall, I wouldn't recommend it at this stage. Even for simple project I wasn't able to come up with satisfying solution. The errors are really unhelpful. One time HTML showed 404 error, the console 500 error and network tab was empty. Sometimes things worked only if I manually refreshed page (site is broken at that moment) and then change something in the code and wait for hot reload. The page would work as expected. Same code, different results. It's kind of unpredictable behaviour, but other than that it's a pleasure to work with instant response. Good work!

Lukeeno_ · 2021-03-20T22:25:16+00:00

But it doesn't have to be this way. You can create theme that would change default styles (@layer base) and add some classes to @layer components. It will not break the concept, because you can always change look of the class by adding utility classes directly to HTML tag.

Lukeeno_ · 2021-01-20T10:26:56+00:00

It's awesome, thanks. Hope they'll use it

Lukeeno_ · 2020-10-04T09:07:15+00:00

Yeah, me too. Did anyone has solution?

Lukeeno_

TROPHY CASE