svelte-preprocess VS imba

svelte-preprocess is responsible for processing things like TypeScript and SCSS. The svelte compiler itself is only responsible for turning the svelte file into JavaScript.

svelte-preprocess should handle scss out-of-the-box, and it’s included in SvelteKit by default if you created your project with create-svelte

Have you tried https://github.com/sveltejs/svelte-preprocess

// svelte.config.js import preprocess from 'svelte-preprocess' import adapter from '@sveltejs/adapter-static' /** @type {import('@sveltejs/kit').Config} */ const config = { // Consult https://github.com/sveltejs/svelte-preprocess // for more information about preprocessors preprocess: [preprocess({ postcss: true })], kit: { // I can even build php file which I can use in current project seamlessly! adapter: adapter({ fallback: 'myapp.php' }), files: { assets: 'src/assets', }, appDir: 'myapp', } } export default config

/** @type {import('@sveltejs/kit').Config} */ const config = { // Consult https://github.com/sveltejs/svelte-preprocess // for more information about preprocessors preprocess: preprocess(),

We need to configure Jest to transform our files. We must explicitly set our test environment to jsdom, which we are using through Jest. Since v27 Jest's default test environment is node. I will put the configuration in a specific Jest configuration file called jest.config.json in the project root folder. If you create a configuration file called jest.config.js, Vite will complain as it expects only ESM JavaScript by default. Vite will recommend that you rename it to a ".cjs" file if you want to do it that way. You can look at the different ways to configure Jest if you are unsure about the file conventions. If you're using TypeScript, you need to configure svelte-preprocess and ts-jest also, see the svelte-jester docs for how to do that.

If you want to write pug, there are tools that allow you to do that: https://github.com/sveltejs/svelte-preprocess

All this file does is export a configuration object for the build of our Svelte application. By default, it uses the svelte-preprocess package, which is a preprocessor for Svelte providing support for PostCSS, SCSS, TypeScript, and much more.

import preprocess from 'svelte-preprocess' import path, { dirname } from 'path' import { fileURLToPath } from 'url' import adapter from '@sveltejs/adapter-node' const filePath = dirname(fileURLToPath(import.meta.url)) const sassPath = `${filePath}/src/lib/style/` const config = { // Consult https://github.com/sveltejs/svelte-preprocess // for more information about preprocessors preprocess: preprocess({ scss: { prependData: `@import '${sassPath}_global-imports.scss';` } }), .... } export default config

import adapter from '@sveltejs/adapter-vercel' import { mdsvex } from 'mdsvex' import preprocess from 'svelte-preprocess' import mdsvexConfig from './mdsvex.config.js' /** @type {import('@sveltejs/kit').Config} */ const config = { extensions: ['.svelte', ...mdsvexConfig.extensions], // Consult https://github.com/sveltejs/svelte-preprocess // for more information about preprocessors preprocess: [ mdsvex(mdsvexConfig), [ preprocess({ postcss: true, }), ], ], kit: { target: '#svelte', adapter: adapter(), }, } export default config // Workaround until SvelteKit uses Vite 2.3.8 (and it's confirmed to fix the Tailwind JIT problem) const mode = process.env.NODE_ENV const dev = mode === 'development' process.env.TAILWIND_MODE = dev ? 'watch' : 'build'

Imba. The best web programming language ever made.

https://imba.io/

I agree. I was looking for the same thing.

They’re not easy to create but side by side code/result demos like the ones I saw on https://imba.io/ make it very clear on what I’ll be getting into as a developer.

You might get away with Svelte (not Sveltekit) here since it compiles down to javascript. Another fun framework to try out for this might be https://imba.io/, which also has an option to compile things down to pure HTML, CSS & JS (plus it’s very fun to work with).

I've been using Svelte exclusively for the past 3 years or so. I love it and will keep using it as my main solution for interactivity. It's fast to use and execute, produces small apps, and it's extremely economical in how you express components.

The confusion the author expresses with $: reactive statements and store auto subscription with the $ are unwarranted IMO. It's really just a lack of familiarity but this kind of stuff becomes intuitive very quickly.

My criticism of Svelte is rather that they haven't gone deep enough into the compiler-based approach.

Would be great if there were something like .svelteStore files where you had all the automatic reactivity tracking without having to use a component. Or some kind of improvements into writing styles. With a compiler you can do anything you want and I think Svelte has been a bit timid, maybe to not scare people away.

For example Imba[1] also bet on a compiler-based approach (years before Svelte existed) and created their own language/framework/compiler. They have come up with amazing solutions to many problems. It's a shame they bet on Ruby aesthetics though and also that they aren't investing into marketing/docs.

Of course, one might argue that using a compiler is a bad idea for a number of reasons. And yeah of course there are objective issues to any approach, but you have to pick your poison. All in all, Svelte has made me tremendously productive compared to using other solutions for years (React, Vue, Mithril, Inferno, etc).

I will say though that I would rather use a solution that doesn't have any reactivity at all. Mithril and Imba have this concept of just "redrawing the whole thing" like a game GUI without having to worry about reactivity. Cognitively speaking, no reactivity is the best mental model IMO. With any reactive solution, it's very easy to fall into complex reactive dependencies which can be hard to track. The author of Imba has a video from 2018 where he talks about this[2].

[1] https://imba.io/

[2] https://www.youtube.com/watch?v=jwoApTLvRdQ

A code snippet showing a simple program right on the home page and "selling" whatever features makes it special would go a long way. It's quite off-putting to have to delve deep into a guide in order to get a feel for a language.

Some examples done right:

https://lfe.io

https://elixir-lang.org

https://imba.io

https://ocaml.org

At the same time, my heart is kind of in the web stuff and I find it a lot more exciting personally so it's hard for me to leave. You can do so much more with web tech and all the new ideas Tcoming from it and the pace it's developing is really . I just don't understand why React is becoming the standard when it's a complete nightmare compared to where we should be. I mean, this is literally insane, especially when things like Svelte exist - or even better, Imba. The day Imba becomes the standard is the day I love web dev again.

Love Imba[0] as well which is the programming language Scrimba is written in. Truly revolutionary.

[0] https://imba.io/