svelte

The list of "who is" is most certainly growing, and there are definitely some bigger names out there: https://github.com/sveltejs/svelte/blob/master/site/src/rout... Jobs listings are cropping up in sundry places too. See for example: https://sveltejobs.dev/jobs/apple-senior-front-end-developer

How does Svelte help with static analysis? Genuinely curious here. I've had my eye on this issue[1] for a while. I'm excited about the idea behind Svelte, but without static typing support, there's no way I could feel comfortable using it on a real project. [1]: https://github.com/sveltejs/svelte/issues/1639

How come there is no TypeScript support, but in the official GitHub repo (https://github.com/sveltejs/svelte) they state: "The compiler is written in TypeScript, but don't let that put you off — it's basically just JavaScript with type annotations."

https://github.com/servo/servo https://github.com/sveltejs/svelte

Thanks for replying. In my previous post, I just wanted to share my experience as someone who has used Svelte (for few days, though, nowhere close to how much you have). 1. I just missed the part of documentation that talks about optional properties. And with undefined and null issue, it's a bit surprising that two-way bindings behave differently that 1-way. Passing null or undefined is convenient when an API gives you such values and they represent empty there. 2. Ok. What I feared is that the tutorial would turn out not to be bugged, and Svelte would be a bad choice for CPU-intensive SPAs. Thanks for reassuring me that's not the case. I'd still love to see the fix for the tutorial bug (because at the first glance, there isn't anything that screams "wrong!" in its code). 3. Yup. I just wanted to point out it's noticeable if you look for

Here is the issue that describes what the Svelte team is doing to add support for TypeScript: https://github.com/sveltejs/svelte/issues/1639

Does anyone know what's the status of Typescript support in Svelte is? This thread is understandably locked: https://github.com/sveltejs/svelte/issues/1639 Still I'm curious. Typescript and RxJS (or MobX) with Svelte as the afterthought (https://michel.codes/blogs/ui-as-an-afterthought) would be a nice combo.

Svelte is: - smaller (it compiles your app, and doesn't include itself in the results) - faster (no virtual DOM, the data to elements are mapped at compile time) - simpler - `age = 30` no boring state management. You're right about the web page - I wanted them to drop 'Cybernetically enhanced web apps' for 'smaller faster simpler' - there was a GitHub issue for it: https://github.com/sveltejs/svelte/issues/3269

I'm migrating one of my sites from jQuery (+ server-generated HTML) to Svelte. I like how Svelte+rollup make it easy to replace just a part of a website (take HTML from a file, put it into Foo.svelte, back in the original file insert <script>new App.Foo({target: document.body, props: { /* data */ }})</script> [0]). Instead of generating HTML, server-side scripts now generate JSON, which could be used later to make a proper API. I don't like handling of "undefined" and "null" values in properties[1]. It would also be nice to have optional properties so that warnings wouldn't get emitted to JS console. Also, someone should investigate iOS bugs[2]. It would be bad if someone made complex site in Svelte+Sapper and only later discovered it lags on iOS. Overall performance is okay, but it's visible to a naked eye that Svelte parts render later

For others who are curious, this is about TypeScript support in Svelte - an issue created a year ago. The following comment by the author sounds hopeful, that they've been working in that direction, and eventually it will happen: https://github.com/sveltejs/svelte/issues/1639#issuecomment-...

Too bad https://github.com/sveltejs/svelte/issues/1639 is still open :)

Yeah, at the very least I expect to see Processes used like Liveview when you need containers/reactors to state and/or run-time control for messages between components. I wonder if an approach like Svelte (https://github.com/sveltejs/svelte) where it compiles into DOM updating code can be enhanced with the concurrency the BEAM provides. It's amazing so much has been done already considering the team only started last February. Writing all those BIFs can't be easy! Lumen is definitely a compelling challenge.

I loved Svelte a few years back and still think it's a nice framework with cool ideas. However, a big issue for me using it at a company is that testing (especially unit testing) seems to be an afterthought. This has made it a non-starter for using it with multiple teams working on same code base. Maybe it's changed with Svelte 3 but a library I wrote for it wasn't clear how to test. (Edit sounds same: https://github.com/sveltejs/svelte/wiki/FAQ#how-do-i-do-test...) JS libraries sometimes take a non-presciptive approach of "test however you want!", But roll your own testing for a UI framework really limits adoption and enthusiasm at larger companies.

Svelte has been production ready for a while now (I've had it in production for 2+ years). Svelte 3 was released 2 months ago, but TypeScript support is still in the works: https://github.com/sveltejs/svelte/issues/1639#issuecomment-...