-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Svelte: previousComponent.$destroy() error #9943
Comments
Just as a heads up, all i did as a quick fix/patch was a check on it: But obviously, that is not a real solution. I did this, just to get work done for now. |
Found out the issue: I had imported my existing webpack and that was causing issues, specifically with the svelte-loader options. Might be a good idea to include in the documentation to not use these options :
That was causing the majority of my problems and it was directly related to the error shown. Once i did this:
Then i was fine, and did not include my custom webpack config. |
Just to add to the great answer by @badman-rodriguez, the My resolve was to unset for (const rule of storybookConfig.module.rules) {
for (const use of (Array.isArray(rule.use) ? rule.use : [rule.use])) {
if (use.loader === 'svelte-loader') {
use.options = {
...use.options,
dev: undefined,
hotReload: undefined,
}
}
}
} |
Bug:
Each time I navigate to another component, this happens:
Which i noticed is here:
From the looks of it, it seems like it doesnt have the $destroy function on there:
Sample Story I used in svelte
Svelte Component
Versions:
Thanks in advance for help!
The text was updated successfully, but these errors were encountered: