Skip to content

enhanced:img should be considered a void element #12255

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

Closed
mquandalle opened this issue May 23, 2024 · 3 comments
Closed

enhanced:img should be considered a void element #12255

mquandalle opened this issue May 23, 2024 · 3 comments

Comments

@mquandalle
Copy link

Describe the bug

Following sveltejs/svelte#11052, svelte now warns on self closing tags for non void elements. This causes a warning when using <enhanced:img />, which is inconsistent with the usage of <img />

Reproduction

image

Logs

No response

System Info

System:
    OS: macOS 14.3.1
    CPU: (8) arm64 Apple M2
    Memory: 83.28 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.16.0/bin/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
    pnpm: 8.14.1 - ~/.nvm/versions/node/v18.16.0/bin/pnpm
    bun: 1.1.3 - ~/.bun/bin/bun
  Browsers:
    Brave Browser: 114.1.52.126
    Safari: 17.3.1
  npmPackages:
    @sveltejs/adapter-vercel: ^5.1.0 => 5.3.0 
    @sveltejs/enhanced-img: ^0.2.0 => 0.2.0 
    @sveltejs/kit: ^2.5.0 => 2.5.9 
    @sveltejs/pancake: ^0.0.18 => 0.0.18 
    @sveltejs/vite-plugin-svelte: ^3.0.2 => 3.1.0 
    svelte: next => 5.0.0-next.137 
    vite: ^5.1.0 => 5.2.11

Severity

annoyance

Additional Information

No response

@mquandalle
Copy link
Author

Probably an issue with https://github.com/sveltejs/language-tools/issues, not SvelteKit

@jasonlyu123
Copy link
Member

Related to sveltejs/language-tools#2321

@mquandalle
Copy link
Author

This issue is fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants