65 |
--------------------------------------------------------------------------------
/webpack.config.js:
--------------------------------------------------------------------------------
1 | const webpack = require('webpack');
2 | const WebpackModules = require('webpack-modules');
3 | const path = require('path');
4 | const config = require('sapper/config/webpack.js');
5 | const pkg = require('./package.json');
6 |
7 | const mode = process.env.NODE_ENV;
8 | const dev = mode === 'development';
9 |
10 | const alias = { svelte: path.resolve('node_modules', 'svelte') };
11 | const extensions = ['.mjs', '.js', '.json', '.svelte', '.html'];
12 | const mainFields = ['svelte', 'module', 'browser', 'main'];
13 | const fileLoaderRule = {
14 | test: /\.(png|jpe?g|gif)$/i,
15 | use: [
16 | 'file-loader',
17 | ]
18 | };
19 |
20 | module.exports = {
21 | client: {
22 | entry: config.client.entry(),
23 | output: config.client.output(),
24 | resolve: { alias, extensions, mainFields },
25 | module: {
26 | rules: [
27 | {
28 | test: /\.(svelte|html)$/,
29 | use: {
30 | loader: 'svelte-loader',
31 | options: {
32 | compilerOptions: {
33 | dev,
34 | hydratable: true
35 | },
36 | // Webpack 4 uses acorn v6 which doesn't work with HMR
37 | // Use overrides from npm or resolutions from yarn to set minimal
38 | // acorn version to v7+
39 | // https://github.com/sveltejs/sapper-template/pull/308
40 | hotReload: false
41 | }
42 | }
43 | },
44 | fileLoaderRule
45 | ]
46 | },
47 | mode,
48 | plugins: [
49 | // pending https://github.com/sveltejs/svelte/issues/2377
50 | // dev && new webpack.HotModuleReplacementPlugin(),
51 | new webpack.DefinePlugin({
52 | 'process.browser': true,
53 | 'process.env.NODE_ENV': JSON.stringify(mode)
54 | }),
55 | ].filter(Boolean),
56 | devtool: dev && 'inline-source-map'
57 | },
58 |
59 | server: {
60 | entry: config.server.entry(),
61 | output: config.server.output(),
62 | target: 'node',
63 | resolve: { alias, extensions, mainFields },
64 | externals: Object.keys(pkg.dependencies).concat('encoding'),
65 | module: {
66 | rules: [
67 | {
68 | test: /\.(svelte|html)$/,
69 | use: {
70 | loader: 'svelte-loader',
71 | options: {
72 | compilerOptions: {
73 | css: false,
74 | generate: 'ssr',
75 | hydratable: true,
76 | dev
77 | },
78 | }
79 | }
80 | },
81 | fileLoaderRule
82 | ]
83 | },
84 | mode,
85 | plugins: [
86 | new WebpackModules()
87 | ],
88 | performance: {
89 | hints: false // it doesn't matter if server.js is large
90 | }
91 | },
92 |
93 | serviceworker: {
94 | entry: config.serviceworker.entry(),
95 | output: config.serviceworker.output(),
96 | mode
97 | }
98 | };
99 |
--------------------------------------------------------------------------------
/src/service-worker.js:
--------------------------------------------------------------------------------
1 | import { timestamp, files, shell } from '@sapper/service-worker';
2 |
3 | const ASSETS = `cache${timestamp}`;
4 |
5 | // `shell` is an array of all the files generated by the bundler,
6 | // `files` is an array of everything in the `static` directory
7 | const to_cache = shell.concat(files);
8 | const staticAssets = new Set(to_cache);
9 |
10 | self.addEventListener('install', event => {
11 | event.waitUntil(
12 | caches
13 | .open(ASSETS)
14 | .then(cache => cache.addAll(to_cache))
15 | .then(() => {
16 | self.skipWaiting();
17 | })
18 | );
19 | });
20 |
21 | self.addEventListener('activate', event => {
22 | event.waitUntil(
23 | caches.keys().then(async keys => {
24 | // delete old caches
25 | for (const key of keys) {
26 | if (key !== ASSETS) await caches.delete(key);
27 | }
28 |
29 | self.clients.claim();
30 | })
31 | );
32 | });
33 |
34 |
35 | /**
36 | * Fetch the asset from the network and store it in the cache.
37 | * Fall back to the cache if the user is offline.
38 | */
39 | async function fetchAndCache(request) {
40 | const cache = await caches.open(`offline${timestamp}`)
41 |
42 | try {
43 | const response = await fetch(request);
44 | cache.put(request, response.clone());
45 | return response;
46 | } catch (err) {
47 | const response = await cache.match(request);
48 | if (response) return response;
49 |
50 | throw err;
51 | }
52 | }
53 |
54 | self.addEventListener('fetch', event => {
55 | if (event.request.method !== 'GET' || event.request.headers.has('range')) return;
56 |
57 | const url = new URL(event.request.url);
58 |
59 | // don't try to handle e.g. data: URIs
60 | const isHttp = url.protocol.startsWith('http');
61 | const isDevServerRequest = url.hostname === self.location.hostname && url.port !== self.location.port;
62 | const isStaticAsset = url.host === self.location.host && staticAssets.has(url.pathname);
63 | const skipBecauseUncached = event.request.cache === 'only-if-cached' && !isStaticAsset;
64 |
65 | if (isHttp && !isDevServerRequest && !skipBecauseUncached) {
66 | event.respondWith(
67 | (async () => {
68 | // always serve static files and bundler-generated assets from cache.
69 | // if your application has other URLs with data that will never change,
70 | // set this variable to true for them and they will only be fetched once.
71 | const cachedAsset = isStaticAsset && await caches.match(event.request);
72 |
73 | // for pages, you might want to serve a shell `service-worker-index.html` file,
74 | // which Sapper has generated for you. It's not right for every
75 | // app, but if it's right for yours then uncomment this section
76 | /*
77 | if (!cachedAsset && url.origin === self.origin && routes.find(route => route.pattern.test(url.pathname))) {
78 | return caches.match('/service-worker-index.html');
79 | }
80 | */
81 |
82 | return cachedAsset || fetchAndCache(event.request);
83 | })()
84 | );
85 | }
86 | });
87 |
--------------------------------------------------------------------------------
/src/routes/blog/_posts.js:
--------------------------------------------------------------------------------
1 | // Ordinarily, you'd generate this data from markdown files in your
2 | // repo, or fetch them from a database of some kind. But in order to
3 | // avoid unnecessary dependencies in the starter template, and in the
4 | // service of obviousness, we're just going to leave it here.
5 |
6 | // This file is called `_posts.js` rather than `posts.js`, because
7 | // we don't want to create an `/blog/posts` route — the leading
8 | // underscore tells Sapper not to do that.
9 |
10 | const posts = [
11 | {
12 | title: 'What is Sapper?',
13 | slug: 'what-is-sapper',
14 | html: `
15 |
First, you have to know what Svelte is. Svelte is a UI framework with a bold new idea: rather than providing a library that you write code with (like React or Vue, for example), it's a compiler that turns your components into highly optimized vanilla JavaScript. If you haven't already read the introductory blog post, you should!
16 |
17 |
Sapper is a Next.js-style framework (more on that here) built around Svelte. It makes it embarrassingly easy to create extremely high performance web apps. Out of the box, you get:
18 |
19 |
20 |
Code-splitting, dynamic imports and hot module replacement, powered by webpack
21 |
Server-side rendering (SSR) with client-side hydration
22 |
Service worker for offline support, and all the PWA bells and whistles
23 |
The nicest development experience you've ever had, or your money back
24 |
25 |
26 |
It's implemented as Express middleware. Everything is set up and waiting for you to get started, but you keep complete control over the server, service worker, webpack config and everything else, so it's as flexible as you need it to be.
In war, the soldiers who build bridges, repair roads, clear minefields and conduct demolitions — all under combat conditions — are known as sappers.
59 |
60 |
For web developers, the stakes are generally lower than those for combat engineers. But we face our own hostile environment: underpowered devices, poor network connections, and the complexity inherent in front-end engineering. Sapper, which is short for Svelte app maker, is your courageous and dutiful ally.
61 | `
62 | },
63 |
64 | {
65 | title: 'How is Sapper different from Next.js?',
66 | slug: 'how-is-sapper-different-from-next',
67 | html: `
68 |
Next.js is a React framework from Vercel, and is the inspiration for Sapper. There are a few notable differences, however:
69 |
70 |
71 |
It's powered by Svelte instead of React, so it's faster and your apps are smaller
72 |
Instead of route masking, we encode route parameters in filenames. For example, the page you're looking at right now is src/routes/blog/[slug].svelte
73 |
As well as pages (Svelte components, which render on server or client), you can create server routes in your routes directory. These are just .js files that export functions corresponding to HTTP methods, and receive Express request and response objects as arguments. This makes it very easy to, for example, add a JSON API such as the one powering this very page
74 |
Links are just <a> elements, rather than framework-specific <Link> components. That means, for example, that this link right here, despite being inside a blob of HTML, works with the router as you'd expect.
75 |
76 | `
77 | },
78 |
79 | {
80 | title: 'How can I get involved?',
81 | slug: 'how-can-i-get-involved',
82 | html: `
83 |
We're so glad you asked! Come on over to the Svelte and Sapper repos, and join us in the Discord chatroom. Everyone is welcome, especially you!
84 | `
85 | }
86 | ];
87 |
88 | posts.forEach(post => {
89 | post.html = post.html.replace(/^\t{3}/gm, '');
90 | });
91 |
92 | export default posts;
93 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # sapper-template
2 |
3 | The default template for setting up a [Sapper](https://github.com/sveltejs/sapper) project. Can use either Rollup or webpack as bundler.
4 |
5 | ## Please note
6 |
7 | Sapper is no longer being actively developed. You may be interested in using Sapper's succesor, [SvelteKit](https://kit.svelte.dev/) for new projects.
8 |
9 | ## Getting started
10 |
11 | ### Using `degit`
12 |
13 | To create a new Sapper project based on Rollup locally, run
14 |
15 | ```bash
16 | npx degit "sveltejs/sapper-template#rollup" my-app
17 | ```
18 |
19 | For a webpack-based project, instead run
20 |
21 | ```bash
22 | npx degit "sveltejs/sapper-template#webpack" my-app
23 | ```
24 |
25 | [`degit`](https://github.com/Rich-Harris/degit) is a scaffolding tool that lets you create a directory from a branch in a repository.
26 |
27 | Replace `my-app` with the path where you wish to create the project.
28 |
29 |
30 | ### Using GitHub templates
31 |
32 | Alternatively, you can create the new project as a GitHub repository using GitHub's template feature.
33 |
34 | Go to either [sapper-template-rollup](https://github.com/sveltejs/sapper-template-rollup) or [sapper-template-webpack](https://github.com/sveltejs/sapper-template-webpack) and click on "Use this template" to create a new project repository initialized by the template.
35 |
36 |
37 | ### Running the project
38 |
39 | Once you have created the project, install dependencies and run the project in development mode:
40 |
41 | ```bash
42 | cd my-app
43 | npm install # or yarn
44 | npm run dev
45 | ```
46 |
47 | This will start the development server on [localhost:3000](http://localhost:3000). Open it and click around.
48 |
49 | You now have a fully functional Sapper project! To get started developing, consult [sapper.svelte.dev](https://sapper.svelte.dev).
50 |
51 | ### Using TypeScript
52 |
53 | By default, the template uses plain JavaScript. If you wish to use TypeScript instead, you need some changes to the project:
54 |
55 | * Add `typescript` as well as typings as dependences in `package.json`
56 | * Configure the bundler to use [`svelte-preprocess`](https://github.com/sveltejs/svelte-preprocess) and transpile the TypeScript code.
57 | * Add a `tsconfig.json` file
58 | * Update the project code to TypeScript
59 |
60 | The template comes with a script that will perform these changes for you by running
61 |
62 | ```bash
63 | node scripts/setupTypeScript.js
64 | ```
65 |
66 | `@sapper` dependencies are resolved through `src/node_modules/@sapper`, which is created during the build. You therefore need to run or build the project once to avoid warnings about missing dependencies.
67 |
68 | The script does not support webpack at the moment.
69 |
70 | ## Directory structure
71 |
72 | Sapper expects to find two directories in the root of your project — `src` and `static`.
73 |
74 |
75 | ### src
76 |
77 | The [src](src) directory contains the entry points for your app — `client.js`, `server.js` and (optionally) a `service-worker.js` — along with a `template.html` file and a `routes` directory.
78 |
79 |
80 | #### src/routes
81 |
82 | This is the heart of your Sapper app. There are two kinds of routes — *pages*, and *server routes*.
83 |
84 | **Pages** are Svelte components written in `.svelte` files. When a user first visits the application, they will be served a server-rendered version of the route in question, plus some JavaScript that 'hydrates' the page and initialises a client-side router. From that point forward, navigating to other pages is handled entirely on the client for a fast, app-like feel. (Sapper will preload and cache the code for these subsequent pages, so that navigation is instantaneous.)
85 |
86 | **Server routes** are modules written in `.js` files, that export functions corresponding to HTTP methods. Each function receives Express `request` and `response` objects as arguments, plus a `next` function. This is useful for creating a JSON API, for example.
87 |
88 | There are three simple rules for naming the files that define your routes:
89 |
90 | * A file called `src/routes/about.svelte` corresponds to the `/about` route. A file called `src/routes/blog/[slug].svelte` corresponds to the `/blog/:slug` route, in which case `params.slug` is available to the route
91 | * The file `src/routes/index.svelte` (or `src/routes/index.js`) corresponds to the root of your app. `src/routes/about/index.svelte` is treated the same as `src/routes/about.svelte`.
92 | * Files and directories with a leading underscore do *not* create routes. This allows you to colocate helper modules and components with the routes that depend on them — for example you could have a file called `src/routes/_helpers/datetime.js` and it would *not* create a `/_helpers/datetime` route.
93 |
94 |
95 | #### src/node_modules/images
96 |
97 | Images added to `src/node_modules/images` can be imported into your code using `import 'images/'`. They will be given a dynamically generated filename containing a hash, allowing for efficient caching and serving the images on a CDN.
98 |
99 | See [`index.svelte`](src/routes/index.svelte) for an example.
100 |
101 |
102 | #### src/node_modules/@sapper
103 |
104 | This directory is managed by Sapper and generated when building. It contains all the code you import from `@sapper` modules.
105 |
106 |
107 | ### static
108 |
109 | The [static](static) directory contains static assets that should be served publicly. Files in this directory will be available directly under the root URL, e.g. an `image.jpg` will be available as `/image.jpg`.
110 |
111 | The default [service-worker.js](src/service-worker.js) will preload and cache these files, by retrieving a list of `files` from the generated manifest:
112 |
113 | ```js
114 | import { files } from '@sapper/service-worker';
115 | ```
116 |
117 | If you have static files you do not want to cache, you should exclude them from this list after importing it (and before passing it to `cache.addAll`).
118 |
119 | Static files are served using [sirv](https://github.com/lukeed/sirv).
120 |
121 |
122 | ## Bundler configuration
123 |
124 | Sapper uses Rollup or webpack to provide code-splitting and dynamic imports, as well as compiling your Svelte components. With webpack, it also provides hot module reloading. As long as you don't do anything daft, you can edit the configuration files to add whatever plugins you'd like.
125 |
126 |
127 | ## Production mode and deployment
128 |
129 | To start a production version of your app, run `npm run build && npm start`. This will disable live reloading, and activate the appropriate bundler plugins.
130 |
131 | You can deploy your application to any environment that supports Node 10 or above. As an example, to deploy to [Vercel Now](https://vercel.com) when using `sapper export`, run these commands:
132 |
133 | ```bash
134 | npm install -g vercel
135 | vercel
136 | ```
137 |
138 | If your app can't be exported to a static site, you can use the [vercel-sapper](https://github.com/thgh/vercel-sapper) builder. You can find instructions on how to do so in its [README](https://github.com/thgh/vercel-sapper#basic-usage).
139 |
140 |
141 | ## Using external components
142 |
143 | When using Svelte components installed from npm, such as [@sveltejs/svelte-virtual-list](https://github.com/sveltejs/svelte-virtual-list), Svelte needs the original component source (rather than any precompiled JavaScript that ships with the component). This allows the component to be rendered server-side, and also keeps your client-side app smaller.
144 |
145 | Because of that, it's essential that the bundler doesn't treat the package as an *external dependency*. You can either modify the `external` option under `server` in [rollup.config.js](rollup.config.js) or the `externals` option in [webpack.config.js](webpack.config.js), or simply install the package to `devDependencies` rather than `dependencies`, which will cause it to get bundled (and therefore compiled) with your app:
146 |
147 | ```bash
148 | npm install -D @sveltejs/svelte-virtual-list
149 | ```
150 |
151 | ## Troubleshooting
152 |
153 | Using Windows and WSL2?
154 |
155 | If your project lives outside the WSL root directory, [this limitation](https://github.com/microsoft/WSL/issues/4169) is known to cause live-reloading to fail. See [this issue](https://github.com/sveltejs/sapper/issues/1150) for details.
156 |
157 | ## Bugs and feedback
158 |
159 | Sapper is in early development, and may have the odd rough edge here and there. Please be vocal over on the [Sapper issue tracker](https://github.com/sveltejs/sapper/issues).
160 |
--------------------------------------------------------------------------------
/scripts/setupTypeScript.js:
--------------------------------------------------------------------------------
1 | /**
2 | * Run this script to convert the project to TypeScript. This is only guaranteed to work
3 | * on the unmodified default template; if you have done code changes you are likely need
4 | * to touch up the generated project manually.
5 | */
6 |
7 | // @ts-check
8 | const fs = require('fs');
9 | const path = require('path');
10 | const { argv } = require('process');
11 |
12 | const projectRoot = argv[2] || path.join(__dirname, '..');
13 |
14 | const isRollup = fs.existsSync(path.join(projectRoot, "rollup.config.js"));
15 |
16 | function warn(message) {
17 | console.warn('Warning: ' + message);
18 | }
19 |
20 | function replaceInFile(fileName, replacements) {
21 | if (fs.existsSync(fileName)) {
22 | let contents = fs.readFileSync(fileName, 'utf8');
23 | let hadUpdates = false;
24 |
25 | replacements.forEach(([from, to]) => {
26 | const newContents = contents.replace(from, to);
27 |
28 | const isAlreadyApplied = typeof to !== 'string' || contents.includes(to);
29 |
30 | if (newContents !== contents) {
31 | contents = newContents;
32 | hadUpdates = true;
33 | } else if (!isAlreadyApplied) {
34 | warn(`Wanted to update "${from}" in ${fileName}, but did not find it.`);
35 | }
36 | });
37 |
38 | if (hadUpdates) {
39 | fs.writeFileSync(fileName, contents);
40 | } else {
41 | console.log(`${fileName} had already been updated.`);
42 | }
43 | } else {
44 | warn(`Wanted to update ${fileName} but the file did not exist.`);
45 | }
46 | }
47 |
48 | function createFile(fileName, contents) {
49 | if (fs.existsSync(fileName)) {
50 | warn(`Wanted to create ${fileName}, but it already existed. Leaving existing file.`);
51 | } else {
52 | fs.writeFileSync(fileName, contents);
53 | }
54 | }
55 |
56 | function addDepsToPackageJson() {
57 | const pkgJSONPath = path.join(projectRoot, 'package.json');
58 | const packageJSON = JSON.parse(fs.readFileSync(pkgJSONPath, 'utf8'));
59 | packageJSON.devDependencies = Object.assign(packageJSON.devDependencies, {
60 | ...(isRollup ? { '@rollup/plugin-typescript': '^6.0.0' } : { 'ts-loader': '^8.0.4' }),
61 | '@tsconfig/svelte': '^1.0.10',
62 | '@types/compression': '^1.7.0',
63 | '@types/node': '^14.11.1',
64 | '@types/polka': '^0.5.1',
65 | 'svelte-check': '^1.0.46',
66 | 'svelte-preprocess': '^4.3.0',
67 | tslib: '^2.0.1',
68 | typescript: '^4.0.3'
69 | });
70 |
71 | // Add script for checking
72 | packageJSON.scripts = Object.assign(packageJSON.scripts, {
73 | validate: 'svelte-check --ignore src/node_modules/@sapper'
74 | });
75 |
76 | // Write the package JSON
77 | fs.writeFileSync(pkgJSONPath, JSON.stringify(packageJSON, null, ' '));
78 | }
79 |
80 | function changeJsExtensionToTs(dir) {
81 | const elements = fs.readdirSync(dir, { withFileTypes: true });
82 |
83 | for (let i = 0; i < elements.length; i++) {
84 | if (elements[i].isDirectory()) {
85 | changeJsExtensionToTs(path.join(dir, elements[i].name));
86 | } else if (elements[i].name.match(/^[^_]((?!json).)*js$/)) {
87 | fs.renameSync(path.join(dir, elements[i].name), path.join(dir, elements[i].name).replace('.js', '.ts'));
88 | }
89 | }
90 | }
91 |
92 | function updateSingleSvelteFile({ view, vars, contextModule }) {
93 | replaceInFile(path.join(projectRoot, 'src', `${view}.svelte`), [
94 | [/(?:/gm, (m, attrs) => ``],
95 | ...(vars ? vars.map(({ name, type }) => [`export let ${name};`, `export let ${name}: ${type};`]) : []),
96 | ...(contextModule ? contextModule.map(({ js, ts }) => [js, ts]) : [])
97 | ]);
98 | }
99 |
100 | // Switch the *.svelte file to use TS
101 | function updateSvelteFiles() {
102 | [
103 | {
104 | view: 'components/Nav',
105 | vars: [{ name: 'segment', type: 'string' }]
106 | },
107 | {
108 | view: 'routes/_layout',
109 | vars: [{ name: 'segment', type: 'string' }]
110 | },
111 | {
112 | view: 'routes/_error',
113 | vars: [
114 | { name: 'status', type: 'number' },
115 | { name: 'error', type: 'Error' }
116 | ]
117 | },
118 | {
119 | view: 'routes/blog/index',
120 | vars: [{ name: 'posts', type: '{ slug: string; title: string, html: any }[]' }],
121 | contextModule: [
122 | {
123 | js: '.then(r => r.json())',
124 | ts: '.then((r: { json: () => any; }) => r.json())'
125 | },
126 | {
127 | js: '.then(posts => {',
128 | ts: '.then((posts: { slug: string; title: string, html: any }[]) => {'
129 | }
130 | ]
131 | },
132 | {
133 | view: 'routes/blog/[slug]',
134 | vars: [{ name: 'post', type: '{ slug: string; title: string, html: any }' }]
135 | }
136 | ].forEach(updateSingleSvelteFile);
137 | }
138 |
139 | function updateRollupConfig() {
140 | // Edit rollup config
141 | replaceInFile(path.join(projectRoot, 'rollup.config.js'), [
142 | // Edit imports
143 | [
144 | /'rollup-plugin-terser';\n(?!import sveltePreprocess)/,
145 | `'rollup-plugin-terser';
146 | import sveltePreprocess from 'svelte-preprocess';
147 | import typescript from '@rollup/plugin-typescript';
148 | `
149 | ],
150 | // Edit inputs
151 | [
152 | /(?`, `self.addEventListener('activate', (event: ExtendableEvent) =>`],
226 | [`self.addEventListener('install', event =>`, `self.addEventListener('install', (event: ExtendableEvent) =>`],
227 | [`addEventListener('fetch', event =>`, `addEventListener('fetch', (event: FetchEvent) =>`],
228 | ]);
229 | }
230 |
231 | function createTsConfig() {
232 | const tsconfig = `{
233 | "extends": "@tsconfig/svelte/tsconfig.json",
234 | "compilerOptions": {
235 | "lib": ["DOM", "ES2017", "WebWorker"]
236 | },
237 | "include": ["src/**/*", "src/node_modules/**/*"],
238 | "exclude": ["node_modules/*", "__sapper__/*", "static/*"]
239 | }`;
240 |
241 | createFile(path.join(projectRoot, 'tsconfig.json'), tsconfig);
242 | }
243 |
244 | // Adds the extension recommendation
245 | function configureVsCode() {
246 | const dir = path.join(projectRoot, '.vscode');
247 |
248 | if (!fs.existsSync(dir)) {
249 | fs.mkdirSync(dir);
250 | }
251 |
252 | createFile(path.join(projectRoot, '.vscode', 'extensions.json'), `{"recommendations": ["svelte.svelte-vscode"]}`);
253 | }
254 |
255 | function deleteThisScript() {
256 | fs.unlinkSync(path.join(__filename));
257 |
258 | // Check for Mac's DS_store file, and if it's the only one left remove it
259 | const remainingFiles = fs.readdirSync(path.join(__dirname));
260 | if (remainingFiles.length === 1 && remainingFiles[0] === '.DS_store') {
261 | fs.unlinkSync(path.join(__dirname, '.DS_store'));
262 | }
263 |
264 | // Check if the scripts folder is empty
265 | if (fs.readdirSync(path.join(__dirname)).length === 0) {
266 | // Remove the scripts folder
267 | fs.rmdirSync(path.join(__dirname));
268 | }
269 | }
270 |
271 | console.log(`Adding TypeScript with ${isRollup ? "Rollup" : "webpack" }...`);
272 |
273 | addDepsToPackageJson();
274 |
275 | changeJsExtensionToTs(path.join(projectRoot, 'src'));
276 |
277 | updateSvelteFiles();
278 |
279 | if (isRollup) {
280 | updateRollupConfig();
281 | } else {
282 | updateWebpackConfig();
283 | }
284 |
285 | updateServiceWorker();
286 |
287 | createTsConfig();
288 |
289 | configureVsCode();
290 |
291 | // Delete this script, but not during testing
292 | if (!argv[2]) {
293 | deleteThisScript();
294 | }
295 |
296 | console.log('Converted to TypeScript.');
297 |
298 | if (fs.existsSync(path.join(projectRoot, 'node_modules'))) {
299 | console.log(`
300 | Next:
301 | 1. run 'npm install' again to install TypeScript dependencies
302 | 2. run 'npm run build' for the @sapper imports in your project to work
303 | `);
304 | }
305 |
--------------------------------------------------------------------------------