-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move site name to a config #36
Comments
And have you tried this brand new version? #20 |
Didn't work:
My config:
Version is the latest:
|
Are you sure you installed npm i svelte-sitemap@next |
Oh, I missed that part. Trying now. |
uh oh, looks like it's building giant single page sitemaps again... also I tried to load my external config as a value and got errors... any way to make this work:
|
And if you try it without importing your config? Just put your domain there and try to build. And what error do you have when you importing config? |
It works fine when I don't include my config other than not splitting the files per the sitemap spec when there are more than 50k pages |
Can you please describe how your whole config file looks like? |
Instead of having the site name in the command which lives in package.json:
"postbuild": "npx svelte-sitemap --domain https://eecue.com"
Could we move it somewhere else that can be populated dynamically at runtime? I use a config file for things like this:
import { config } from '$lib/config';
Ideally I could use that to populate the domain.
The text was updated successfully, but these errors were encountered: