-
-
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
Scan output build folder instead of src/routes #1
Comments
Thank you @auderer You can install next version like this: |
I am using the vercel adapter with its own build output folder. Would be great if we can customize the build dir. |
@tonprince Good point! But I consider this issue closed, so I made a new one. Let's discuss there #3 |
This approach is nice but the vercel adapter does not generate html files |
@100lvlmaster You are right, the Vercel adapter does not generate static files and my library is intended just for the Static Adapter. I personally do not use the Vercel plugin but maybe it could be used only in a specific combination with a static adapter... (I know it won't be a very common case) But of course if there are no static files, then my library will not work either. |
Currently this package scans the
src/routes
folder to generate the sitemap. This works fine for normal pages, but it doesn't work for dynamically generated pages like[slug].svelte
, etc.Instead, we should scan the
build
folder. Here's a demo script that does this:We should use a method like this instead of routes, as it will capture the actual output from Svelte, which can differ greatly from the source files.
The text was updated successfully, but these errors were encountered: