svelte:options customElement about gdpr-cookie-consent-banner HOT 9 OPEN

is it an error or a warning?

a bit annoying, but if we want to publish the banner as a WebComponent too, we need to include that. I'm not sure there is a way around it.

from gdpr-cookie-consent-banner.

Hi,

Sorry it was a warning.

Might I suggest appending to your Svelte example the modification to svelte.config.js in the Readme.md.

Thanks for the update,

Pierre

from gdpr-cookie-consent-banner.

It says in the warning what you need to do, so not sure this is necessary.

I feel like this is an issue within the way Svelte works, since you don't actually want custom element output in a regular svelte project.

the compiler should know that you're seeing the options tag in a project dependency, not the main project, and not warn.

i'll raise an issue with Svelte (or you can)

from gdpr-cookie-consent-banner.

@antony did you make an issue?

from gdpr-cookie-consent-banner.

from gdpr-cookie-consent-banner.

Not sure if this is related but I cannot use the cookie banner because of the following issue:

from gdpr-cookie-consent-banner.

Actually solved, seems I used an old version of sveltekit

from gdpr-cookie-consent-banner.

Still shows an error on latest sveltekit "@sveltejs/kit": "^2.5.0".
The problem with this is once I add

compilerOptions: {
customElement: true,
},

pre-rendering with static adapter kit breaks and CSS is no longer loaded from Svelte pages and components.

from gdpr-cookie-consent-banner.

@belte42 because you're trying to mark your entire project as a custom element, which won't work. The "did you forget to add" customElement: true warning is just a warning, and can be safely ignored.

If it bothers you a lot, please raise a SvelteKit issue and I'll discuss it with the others and see if I can implement a fix - but at the moment, I don't have time to do it.

from gdpr-cookie-consent-banner.