Skip to content
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(missing-declaration) #6

Closed
el3um4s opened this issue Jun 23, 2021 · 2 comments · Fixed by #8
Closed

svelte(missing-declaration) #6

el3um4s opened this issue Jun 23, 2021 · 2 comments · Fixed by #8

Comments

@el3um4s
Copy link

el3um4s commented Jun 23, 2021

I have created a Test.svelte component

<script lang="ts">
    export let hello:string = "World"
</script>

<div>{hello}</div>

I have this worning in VScode

image

Then I imported the component into App.svelte

<script lang="ts">
  import Test from "./Test.svelte";
  export let name: string;
</script>

<main>
  <h1>Hello {name}!</h1>
  <p>Visit the <a href="https://svelte.dev/tutorial">Svelte tutorial</a> to learn how to build Svelte apps.</p>
  <Test />
</main>

I have this worning in VScode

image

By searching I found this hypothesis for a solution

Getting svelte(missing-declaration) warnings for props

But I don't know how to do it.

SilentEchoGM added a commit to SilentEchoGM/electron-svelte-typescript that referenced this issue Sep 27, 2021
@SilentEchoGM
Copy link
Contributor

SilentEchoGM commented Sep 27, 2021

Accidentally fixed this while resolving a path aliasing problem that had the same root cause so submitted a pull request that appears to solve it without affecting anything else by just shuffling the config files around

fuzzc0re added a commit that referenced this issue Sep 28, 2021
@fuzzc0re
Copy link
Owner

Thanks for the help @SilentEchoUK
Closing the issue due to 7aee0f9

@fuzzc0re fuzzc0re linked a pull request Sep 28, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants