Import in service-worker.ts from $lib throws

[frederikhors]

Describe the bug

If I import this:

import { myFunc } from "$lib/utils";

in service-worker.ts, it throws like this:

[vite]: Rollup failed to resolve import "$lib/utils" from "src\service-worker.ts".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`

Why?

System Info

System:
    OS: Windows 10 10.0.19043
  Binaries:
    Node: 14.17.5 - C:\Program Files\nodejs\node.EXE
    npm: 7.21.0 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    @sveltejs/adapter-static: 1.0.0-next.17 => 1.0.0-next.17
    @sveltejs/kit: 1.0.0-next.159 => 1.0.0-next.159
    svelte: 3.42.4 => 3.42.4

Severity

serious, but I can work around it

[JeanJPNM]

I found the issue:

Here are the aliases for the client bundle:

kit/packages/kit/src/core/build/index.js

Lines 169 to 174 in c086b18

	resolve: {
	alias: {
	$app: path.resolve(`${build_dir}/runtime/app`),
	$lib: config.kit.files.lib
	}
	},

Here are the aliases for the server bundle:

kit/packages/kit/src/core/build/index.js

Lines 484 to 489 in c086b18

	resolve: {
	alias: {
	$app: path.resolve(`${build_dir}/runtime/app`),
	$lib: config.kit.files.lib
	}
	},

And here are the aliases for the service worker:

kit/packages/kit/src/core/build/index.js

Lines 607 to 611 in c086b18

	resolve: {
	alias: {
	'$service-worker': path.resolve(`${build_dir}/runtime/service-worker`)
	}
	}

As you can see, the rollup config for the service worker bundle doesn't include the $lib alias like the other two, I don't know if this is an error or is there by design.

But I if it is a bug I will happily open a pr.

[JeanJPNM]

Thinking about it, it is problably a bug.