--- title: SvelteKit pagination_prev: demos/net/index pagination_next: demos/mobile/index --- import current from '/version.js'; import CodeBlock from '@theme/CodeBlock'; :::note This demo covers SvelteKit. The [Svelte demo](/docs/demos/frontend/svelte) covers general client-side strategies. This demo uses ["Base64 Loader"](/docs/demos/static/vitejs#base64-loader) from the ViteJS demo. ::: SvelteKit projects use ViteJS under the hood. They expose the `vite.config.js` script. The [ViteJS demo](/docs/demos/static/vitejs) examples work as expected! The following diagram depicts the workbook waltz: ```mermaid flowchart LR file[(workbook\nfile)] subgraph SheetJS operations base64(base64\nstring) aoo(array of\nobjects) end html{{HTML\nTABLE}} file --> |vite.config.js\ndata loader| base64 base64 --> |+page.server.js\nload function| aoo aoo --> |+page.svelte\ncomponent| html ``` ## Integration `+page.server.js` scripts can be pre-rendered by exporting `prerender` from the script. If the SheetJS operations are performed in the server script, only the results will be added to the generated pages! For static site generation, `@sveltejs/adapter-static` must be used. ### Loader :::note The ViteJS demo used the query `?b64` to identify files. To play nice with SvelteKit, this demo matches the file extensions directly. ::: The loader should be added to `vite.config.js`. The code is nearly identical to the ["Base64 Loader" ViteJS example.](/docs/demos/static/vitejs#base64-loader) ```js title="vite.config.js" import { sveltekit } from '@sveltejs/kit/vite'; import { defineConfig } from 'vite'; import { readFileSync } from 'fs'; export default defineConfig({ assetsInclude: ['**/*.numbers', '**/*.xlsx'], plugins: [sveltekit(), { name: "sheet-base64", transform(code, id) { if(!id.match(/\.(numbers|xlsx)$/)) return; var data = readFileSync(id, "base64"); return `export default '${data}'`; } }] }); ``` #### Types For VSCodium integration, types can be specified in `src/app.d.ts`. The example data loader returns Base64 strings. Declarations should be added for each file extension supported in the loader: ```ts title="src/app.d.ts" declare global { declare module '*.numbers' { const data: string; export default data; } declare module '*.xlsx' { const data: string; export default data; } } ``` ### Data Processing For static sites, SheetJS operations should be run in `+page.server.js` . Assuming `pres.xlsx` is stored in the `data` directory from the project root, the relative import ```js import b64 from "../../data/pres.xlsx" ``` will return a Base64 string which can be parsed in the script. The workbook object can be post-processed using utility functions. The following example uses `sheet_to_json` to generate arrays of row objects for each worksheet. The data presented to the page will be an object whose keys are worksheet names: ```js title="src/routes/+page.server.js" import b64 from "../../data/pres.xlsx"; import { read, utils } from "xlsx"; export const prerender = true; /** @type {import('./$types').PageServerLoad} */ export async function load({ params }) { const wb = read(b64); /** @type {[string, any[]][]} */ const data = wb.SheetNames.map(n => [n, utils.sheet_to_json(wb.Sheets[n])]); return Object.fromEntries(data); } ``` ### Data Rendering The shape of the data is determined by the loader. The example loader returns an object whose keys are worksheet names and whose values are arrays of objects. Using standard Svelte patterns, HTML tables can be generated from the data: ```html title="src/routes/+page.svelte"
Name | Index | {#each pres as p}
---|---|
{p.Name} | {p.Index} |