Publish new NPM version 3.0.0

[ComFreek]

The latest NPM version is 2.1.0 (published 3 years ago), the version specified in package.json in latest commits is 1.x.y (for some values of x, y I forgot). That version mismatch is particularly confusing.

What do you think about bumping the version in package.json to 3.0.0 and releasing a new NPM package version?

[jpaulm]

Thanks so much for digging into this and for the updates, Comfreek!

Good idea to bump the version in package.json! I need to look up how to release a new NPM package version - I will get onto that early next week - this weekend is a bit hectic!

Best regards,

Paul

On Sat, Jul 6, 2019 at 4:01 AM ComFreek [email protected] wrote:

The latest NPM version is 2.1.0 (published 3 years ago), the version specified in package.json in latest commits is 1.x.y (for some values of x, y I forgot). That version mismatch is particularly confusing.

What do you think about bumping the version in package.json to 3.0.0 and releasing a new NPM package version?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jpaulm/jsfbp/issues/85?email_source=notifications&email_token=AACMMJ2J34O7BSQ5HKI2KBDP6BGMZA5CNFSM4H6S3DJ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G5UXWXQ, or mute the thread https://github.com/notifications/unsubscribe-auth/AACMMJ7R2ME4MY4HYVKALBDP6BGMZANCNFSM4H6S3DJQ .

[jpaulm]

I assume you are talking about the version no. in package.json line 2? I am not sure how this ties in with the version no. of NPM - everything in that file has a different version no.! Also do I just create a new npm package, or update the old one? Thanks

[ComFreek]

Yes, exactly, that line 2.

everything in that file has a different version no.!

Precisely! That's why it's confusing :smile: I think the procedure would be

1. Bump that version number in package.json, line 2 to, say, 3.0.0.
2. Run npm install (to update package-lock.json as well)
3. Follow the usual publishing procedure for NPM packages. I don't know that by heart, sorry, would need to look it up as well.

[jpaulm]

Thanks! It's been so long that I've forgotten everything!

I recently transferred to Win 10, and it looks like everything has to be rebuilt!

Now it's saying something about needing V141 build tools! Someone suggested installing Visual Studio 2017, but I have that!

I noticed that I don't have a node-modules/fibers directory, so I trid npm install fibers, and I get the same message about v141!

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Platform.targets(57,5): error MSB8020: The build t ools for v141 (Platform Toolset = 'v141') cannot be found. To build using the v141 build tools, please install v141 bui ld tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-cli ck the solution, and then selecting "Retarget solution". [C:\Users\Paul\Documents\GitHub\jsfbp\node_modules\fibers\buil d\fibers.vcxproj]

Looks like I have to create a Visual Studio project, but what should it be called...?

Can you get me started...?!

TIA,

Paul

On Mon, Jul 8, 2019 at 2:37 AM ComFreek [email protected] wrote:

Yes, exactly, that line 2.

everything in that file has a different version no.!

Precisely! That's why it's confusing 😄 I think the procedure would be

1. Bump that version number in package.json, line 2 to, say, 3.0.0.
2. Run npm install (to update package-lock.json as well)
3. Follow the usual publishing procedure for NPM packages. I don't know that by heart, sorry, would need to look it up as well.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jpaulm/jsfbp/issues/85?email_source=notifications&email_token=AACMMJ5Q7OFW7OX2RVRED43P6LODNA5CNFSM4H6S3DJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZMDTMA#issuecomment-509098416, or mute the thread https://github.com/notifications/unsubscribe-auth/AACMMJ45I5RJ6JNQKN7DAELP6LODNANCNFSM4H6S3DJQ .