Mat Ryer makes the case for passive user preferences, which is where you store their last used setting for them without asking and then set it as the default the next time they interact with that part of your app. He then goes on to describe how they accomplish this with Svelte. Good stuff!
Orta Therox, making the big announcement on behalf of the Svelte team:
Up until now TypeScript was usable with Svelte, but not officially supported by the project. What does that official support look like?
- You can use TypeScript inside your
<script>blocks — just add the
- Components with TypeScript can be type-checked with the
- You get autocompletion hints and type-checking as you’re writing components, even in expressions inside markup
- TypeScript files understand the Svelte component API — no more red squiggles when you import a
.sveltefile into a
I know a lot of people have been waiting for this. Congrats to all involved on a big release!
We often try new frameworks and tools in side projects or throwaway contexts, but you don’t learn that much about a thing until you use it to build something real. That’s why we have Mat Ryer and David Hernandez joining us to share their experience of using Svelte while building their new startup, Pace.dev.
This is a well-reasoned piece that includes Svelte’s advantages, disadvantages, and drawbacks today.
Is using bleeding edge tech risky and foolish? How much blood are we talking about? My experience tells me Svelte is a safe choice, more leading edge than bleeding. However I’m more risk tolerant than most people, I have a lot of experience with JS frameworks, and our team is motivated, so we can deal with rough edges.
My goal is to start a community-driven language-learning platform that gives it’s users and contributors a way to influence it’s future and adapt it to special requirements.
Once course content is properly decoupled from the software, it should be possible to experiment with alternative ways of using course content: for example, the creation of audiobooks or print material.
The Spanish course is already started for demo purposes
The goal of
svelvetis to make
svelteplay nicely with
As of today, svelte depends on a loader for webpack or rollup which compiles your svelte components into individual js files. Since snowpack’s goal is to avoid the need for a bundler, we can’t use those loaders, but we can use svelte’s internal compiler api to do 95% of the work for us. On top of that,
svelvetadds automatic file watching to recompile your svelte files just like a loader would, but much faster!
I’m not gonna lie, any green field that offers a super light build process is looking pretty stinkin’ green these days. That being said, there’s a reason we call it the bleeding edge.
Jerod, Divya, Chris, KBall, & Nick ring in the new year with our 2020 predictions, wish lists, & resolutions. Will Chrome’s browser market share decrease? Will Svelte (or a Svelte-alike) continue to trend? Will Jerod finally write some TypeScript?! Listen along and let us know your thoughts on the matters.
Results are in for the 2019 State of JS survey. I’ve been digging through charts to see what I can see. Here are 7 insights that jumped off the page to me.
A nice side-by-side comparison of a simple todo app built with both frameworks. If you’ve experimented with these tools, you’ll probably find this article too elementary to be useful, but if either is unfamiliar to you, definitely give it a read.
After several months of being just days away, we are over the moon to announce the stable release of Svelte 3. This is a huge release representing hundreds of hours of work by many people in the Svelte community, including invaluable feedback from beta testers who have helped shape the design every step of the way.
Lots of folks (myself included) have been eagerly awaiting this release after Rich teed it up on The Changelog #332. We’d love to hear your first impressions!