Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

Handling configuration in Sapper #1216

Closed
benmccann opened this issue May 21, 2020 · 3 comments
Closed

Handling configuration in Sapper #1216

benmccann opened this issue May 21, 2020 · 3 comments

Comments

@benmccann
Copy link
Member

benmccann commented May 21, 2020

Background

There are a number of PRs or open issues that would require providing a configuration option. We should handle configuration in a well-thought out and consistent manner.

language-tools already uses a svelte.config.js and Svelte was considering adopting it more widely.

I'm assuming that we would use a .config.js because it's inline with the existing svelte.config.js and also because it's more flexible and allows providing additional types (e.g. function)

RFC

Please see the RFC for a proposed implementation and list of Sapper PRs that might be affected

@antony
Copy link
Member

antony commented May 21, 2020

Dare I say this sounds a bit like an RFC?

@benmccann
Copy link
Member Author

RFC submitted!

@benmccann
Copy link
Member Author

SvelteKit has a svelte.config.cjs file to address this

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants