package.json dependency version should be changed

[miken32]

It's not installing beta 2 for me. Perhaps change it to ^4.0.0-beta instead of something specific like 4.0.0-beta.1 for the duration of the beta period?

[miken32]

Hmm scratch that, I was misreading the beta1 in dependencies. Something isn't working for me though...

[miken32]

Ok the datatables.net-buttons-bs5 version 4.0.0-beta1 that I'm getting from npm (which doesn't seem to have a tag on this repo) has these dependencies:

    "dependencies": {
        "datatables.net-buttons": "4.0.0-beta.1",
        "datatables.net-bs5": "3.0.0-beta.1"
    },

So the problem is the 3.0.0-beta.1 instead of 3.0.0-beta.2 or ^3.0.0-beta.

Likewise, dependencies for datatables.net-bs5 are:

    "dependencies": {
        "datatables.net": "3.0.0-beta.1"
    },

instead of 3.0.0-beta.2 or ^3.0.0-beta.

[AllanJard]

Yeah sorry - unfortunately when I was getting these packages ready for release alongside DataTables 3 beta.1 I tied them to DataTables 3.0.0-beta.1 rather than allowing them to use the latest beta, which was a total footgun. I probably need to go through the packages changing that and re-releasing them as a new beta. Apologies for the oversight!

[miken32]

No problem, I'm looking forward to being able to do some more testing once it's sorted out!

[miken32]

Any news on moving forward with updated beta releases @AllanJard ?

[AllanJard]

Apologies, I've not been able to do this yet. I did have a quick look and see that the package.json file is correct now, I just need to get it tagged up, but for a variety of reasons I've not yet been able to do it. Hopefully not too far away.

[miken32]

Any chance we'll see a beta/rc release before 3.0 goes live? I've tried a few things to get npm to install the main branch into my project without success, so am unable to do any further testing without updated beta versions showing up at npmjs.com