I implemented a 'version' npm script to ensure that the 'latest' npm version always contains the latest [automatically] built dist/nem-sdk.js.
This is to ensure that releasing a new version always contain the latest built SDK in the dist/ folder.
As a matter of fact, I see myself commiting over 1400 lines in that dist/ folder (because i needed to bump version in order to publish..) -
if you'd prefer, I could send a PR with just the 1st commit. Then you would need to create an account on npmjs, i would add you as a contributor and you could then merge my change and bump to version yourself. tell me :)
I implemented a 'version' npm script to ensure that the 'latest' npm version always contains the latest [automatically] built dist/nem-sdk.js.
This is to ensure that releasing a new version always contain the latest built SDK in the dist/ folder.
As a matter of fact, I see myself commiting over 1400 lines in that dist/ folder (because i needed to bump version in order to publish..) - if you'd prefer, I could send a PR with just the 1st commit. Then you would need to create an account on npmjs, i would add you as a contributor and you could then merge my change and bump to version yourself. tell me :)
Have a great day!