Single-line `@import` comment no longer valid in 50.6.10

[zorac]

Expected behavior

Single-line @import jsdoc comments should be considered valid, and the import(s) visible to later @type etc jsdoc comments.

Actual behavior

A single-line @import comment triggers a Bad @import tag warning from jsdoc/check-values.

A later @type commment using that import triggers a The type '<type>' is undefined warning from jsdoc/no-undefined-types.

Neither of these warnings appear when using version 50.6.9 of the plugin, or if the @import tag is used in a multi-line comment.

ESLint Config

import jsdoc from 'eslint-plugin-jsdoc'

export default [
    jsdoc.configs['flat/recommended'],
]

ESLint sample

This code generates warnings:

/** @import { ReactNode } from 'react' */

/** @type {ReactNode} */
export const TEST = null

This code does not generate warnings:

/**
 * @import { ReactNode } from 'react'
 */

/** @type {ReactNode} */
export const TEST = null

Environment

• Node version: v23.10.0
• ESLint version: v9.25.1
• eslint-plugin-jsdoc version: 50.6.10

[github-actions]

🎉 This issue has been resolved in version 50.6.11 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[JounQin]

I'm still meeting this issue with:

// @ts-check

/** @import { Config, Plugin } from 'prettier' */

import base from '@1stg/prettier-config/semi';
import * as jsdoc from 'prettier-plugin-jsdoc';
import * as jsdocType from 'prettier-plugin-jsdoc-type';
import * as svelte from 'prettier-plugin-svelte';

/** @type {Config} */
const config = {
  ...base,
  plugins: [
    .../** @type {Plugin[]} */ (base.plugins),
    jsdoc,
    jsdocType,
    svelte,
  ],
};

export default config;

  10:1  warning  The type 'Config' is undefined  jsdoc/no-undefined-types
  14:1  warning  The type 'Plugin' is undefined  jsdoc/no-undefined-types

[github-actions]

🎉 This issue has been resolved in version 50.6.12 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[brettz9]

@JounQin : Sorry, had missed applying to that rule as well. Fixed.