svelte-preprocess VS svelte-i18n

You can learn more about the official svelte-preprocess and other available config here

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

// svelte.config.js import sveltePreprocess from 'svelte-preprocess' export default { // Consult https://github.com/sveltejs/svelte-preprocess // for more information about preprocessors // **here -> postcss: true** preprocess: sveltePreprocess({ postcss: true, }) }

/** @type {import('@sveltejs/kit').Config} */ const config = { // Consult https://github.com/sveltejs/svelte-preprocess // for more information about preprocessors preprocess: preprocess({ typescript: true, postcss: true, scss: { prependData: @import 'src/styles/helpers/functions.scss'; } }), kit: { paths: { assets: '', base: dev ? '' : '/route/in/website' }, trailingSlash: 'always', adapter: adapter({ pages: 'build', assets: 'build', fallback: 'index.html' }), files: { hooks: 'src/hooks', }, prerender: { default: true, }, } };

Continue to use tags

In svelte.config.js ... (import aliases can be whatever you want)

1. import svelte_preprocess from 'svelte-preprocess'
2. import autoprefixer from 'autoprefixer'
3. pass the Svelte preprocessor to Kit's preprocess config option and pass the postcss plugin to that Svelte preprocessor:

svelte.config.js

import svelte_proprocess from 'svelte-process'
import autoprefixer from 'autoprefixer'

const config = {
    // Consult https://github.com/sveltejs/svelte-preprocess for more info
    preprocess: [
        svelte_preprocess({
            postcss: {
                plugins: [autoprefixer()]
            }
        })
    ]
}

import adapter from '@sveltejs/adapter-auto'; import preprocess from 'svelte-preprocess'; import { mdsvex } from 'mdsvex'; import remarkMath from 'remark-math'; import rehypeKatex from 'rehype-katex-svelte'; /** @type {import('@sveltejs/kit').Config} */ const config = { extensions: ['.svelte', '.svx', '.md'], // Consult https://github.com/sveltejs/svelte-preprocess // for more information about preprocessors preprocess: [ preprocess(), mdsvex({ extensions: ['.svx', '.md'], smartypants: true, layout: { project: "./src/routes/projects/layout.svelte", post: "./src/routes/blog/layout.svelte", }, remarkPlugins: [remarkMath], rehypePlugins: [rehypeKatex], }), ], kit: { adapter: adapter({ edge: false, external: [], split: false }) } }; export default config;

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

// We have changed the adapter line to use adapter-node@next import adapter from '@sveltejs/adapter-node@next'; import preprocess from 'svelte-preprocess'; /** @type {import('@sveltejs/kit').Config} */ const config = { // Consult https://github.com/sveltejs/svelte-preprocess // for more information about preprocessors preprocess: preprocess(), kit: { // We have changed this to point to a build directory adapter: adapter({ out: 'build' }) } }; export default config;

Yeah I'm just using svelte-18n

Make sure you have Node.js and npm installed. It's best, if you have some experience with simple HTML, JavaScript and basic Svelte, before jumping to svelte-i18n.

There are some great i18n libraries which can be used together with SvelteKit, such as svelte-i18n, typesafe-i18n or svelte-intl-precompile. However, a month ago, I decided to create my own, modular and lightweight one, because i was missing some features like dynamic translations load (load translations for visited pages only), custom translation sources (e.g. external API) or component scoped translations, etc...

I had reasonable success with https://github.com/kaisermann/svelte-i18n in one of my pet projects.

With the svelte-i18n library internationalization of a Svelte / Sapper apps has gotten a lot better, but there has been an omission in solutions for routing languages (despite long discussions). I would like to share our solution for making internationalized routing: