DataTables logo
≡

Incorrect version of the DataTable.net package from npm (3.2.2 instead of 3.0.1)

Incorrect version of the DataTable.net package from npm (3.2.2 instead of 3.0.1)

sloloslolo Posts: 143Questions: 28Answers: 2
in DataTables

Link to test case: NA
Debugger code (debug.datatables.net): NA
Error messages shown: NA
Description of problem:

Hello,

I’m not sure if the issue is on my end or with the npm repo, but there seems to be a problem with the version number of the "datatables.net-bs4" package (see screenshot below).

Could you confirm the issue?

Thanks, and have a great day.

Replies

  • allanallan Posts: 65,891Questions: 1Answers: 10,962 Site admin

    What package manager are you using, and what version?

    Many years ago I managed to release a version with the 3.2.2 tag incorrectly. It was deprecated quickly, but npm wouldn't allow it to be completely removed. The deprecated flag on it means I shouldn't be used, but some old package managers still do (one of the online ones had the problem, although I can't recall off the top of my head which one).

    Allan

  • allanallan Posts: 65,891Questions: 1Answers: 10,962 Site admin

    Hmm, the fact that it is the bs4 package makes me wonder about that one and it's deprecation flag. I'll look into it!

  • allanallan Posts: 65,891Questions: 1Answers: 10,962 Site admin

    No, the incorrect 3.2.2 release was deprecated 10 years ago. Package managers should be ignoring it.

    Allan

  • sloloslolo Posts: 143Questions: 28Answers: 2

    I use npm to manage my packages.

    node -v : v22.22.3
    npm -v : 11.18.0

    npm update datatables.net-bs4

    npm warn deprecated datatables.net-bs4@3.2.2: Incorrect version published. Please use the latest non-deprecated version - 1.10.13 at the time of writing

    changed 1 package, and audited 129 packages in 3s

    7 packages are looking for funding
    run npm fund for details

    found 0 vulnerabilities

    So I decided to unistall and install it again

    npm uninstall datatables.net-bs4
npm install --save-dev datatables.net-bs4

    And no more problem.

    Sorry for the inconvenience.

  • allanallan Posts: 65,891Questions: 1Answers: 10,962 Site admin

    Interesting. I'm looking forward to version 3.2.3 so that mistake will not rear it's head again!

    Allan

  • sloloslolo Posts: 143Questions: 28Answers: 2

    It's really strange; this morning I ran npm outdated and the datatables.net-bs4 package reappeared.

  • allanallan Posts: 65,891Questions: 1Answers: 10,962 Site admin

    Sounds like npm outdated isn't taking into account the deprecated flag. I'll try it locally later on. Many thanks for the information.

    Allan

  • allanallan Posts: 65,891Questions: 1Answers: 10,962 Site admin

    I've just tried the following with npm 11.17.0 and 11.12.1:

    mkdir temp
cd temp
npm init -y
npm install datatables.net-bs4
npm outdated

    and nothing shows up as outdated. That is what I would expect and hope for, but doesn't seem to align with what you are seeing.

    Is that basically the same sequence as you are using? I did see you have --save-dev as well, and I tried that as well, but no luck in reproducing the problem with that flag either).

    Allan

Sign In or Register to comment.