fix: Keep inlined JSDoc comments in property conversion of svelte-migrate

[rgieseke]

This addresses trailing inlined JSDoc property descriptions being deleted by svelte-migrate, see #15530.

Previously:

/** @type {number} [comment_default_value=1] - This has a comment and a default value. */
export let comment_default_value = 1;```

The comment would be removed in the migrated version:

/**
* @typedef {Object} Props
* @property {number} [comment_default_value].
*/

/** @type {Props} */
let { comment_default_value = 1 } = $props();

With the change in this PR it becomes the following:

/**
* @typedef {Object} Props
* @property {number} [comment_default_value] - This has a comment and a default value.
*/

/** @type {Props} */
let { comment_default_value = 1 } = $props();

The default value description in the JSDoc is still removed, but that's probably ok, as the default value is still in the declaration below.

Happy to change this if you can guide me to a different solution. The regex used here could also potentially be improved to handle more cases of (multiple) whitespace, but wanted to start a discussion first.

The style of JSDoc comments is used in Layer Cake. The components are vendored in other projects so there are lots of repos out there who use this kind of comment (e.g. GitHub search for AxisX.svelte)

[changeset-bot]

🦋 Changeset detected

Latest commit: 8cac71e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
svelte	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-svelte-15567-svelte.vercel.app/

[Rich-Harris]

thank you!

[patriciatiffany]

Thanks for doing this!! This fix was what I'd been looking out for. Since I've been migrating to Svelte 5 one component at a time, I'm using the VScode extension-- how soon should I expect that to contain these change?

[rgieseke]

I think this should work from VS Code once the project is updated to a Svelte version with this change (from 5.24.0).