datatables shows up with funny version in npm outdated

datatables shows up with funny version in npm outdated

guidoriceguidorice Posts: 8Questions: 4Answers: 1

Hi, I am wondering why npm outdated shows a version 3.2.2. Isn't 1.10.13 the latest version of the core datatables?

Package                          Current   Wanted            Latest
datatables.net                   1.10.13  1.10.13             3.2.2 
datatables.net-bs                1.10.13  1.10.13             3.2.2

This question has an accepted answers - jump to answer

Answers

  • allanallan Posts: 63,839Questions: 1Answers: 10,518 Site admin
    Answer ✓

    Yeah - it looks like there has been some tag pollution unfortunately. Issue about it here.

    I'll probably need to do a new release to fix it properly, but I'm travelling at the moment so it won't be until the new year I'm afraid.

    Allan

  • guidoriceguidorice Posts: 8Questions: 4Answers: 1

    Awesome- glad to hear it is a known issue. I will not worry about it any more :) Have a good New Year holiday and safe travels.

  • allanallan Posts: 63,839Questions: 1Answers: 10,518 Site admin

    This should be fixed now :smile:.

    Happy New Year!

    Allan

  • rink_attendant_6rink_attendant_6 Posts: 16Questions: 4Answers: 1

    The issue appears to be happening again, but at 2.1.1:

    Package                       Current   Wanted  Latest  Location
    console-stamp                   0.2.4    0.2.5   0.2.5 
    datatables.net                1.10.12  1.10.12   2.1.1
    datatables.net-buttons          1.2.2    1.2.2   1.2.4
    datatables.net-buttons-dt       1.2.2    1.2.2   1.2.4
    datatables.net-dt             1.10.12  1.10.12   2.1.1
    datatables.net-responsive       2.1.0    2.1.0   2.1.1
    datatables.net-responsive-dt    2.1.0    2.1.0   2.1.1
    
  • allanallan Posts: 63,839Questions: 1Answers: 10,518 Site admin

    Yes, I spotted this yesterday as well and have been trying to rectify the issue, but I'm having problems unpublishing the wrong packages and have a support request in with the npm folks to see what is going on there.

    I think it was caused by a typo in my automated build script which has been fixed now, but want to remove those packages and do a little more testing before I say that for certain.

    Allan

This discussion has been closed.