I've noticed that packaged npm module version 1.0.0 does not contain up-to-date code changes from my recent PR. Has the build process actually taken the latest code? Because when I look at downloaded module built source code it seems it's transpiled against an older source code.
Hi mdibaiee,
I've noticed that packaged npm module version 1.0.0 does not contain up-to-date code changes from my recent PR. Has the build process actually taken the latest code? Because when I look at downloaded module built source code it seems it's transpiled against an older source code.
Woops, sorry, you are right, I didn't run grunt before deploying the latest version, thanks for noting. Published node-telegram-api@1.0.1, feel free to re-open if the issue still persists. 😁
Woops, sorry, you are right, I didn't run `grunt` before deploying the latest version, thanks for noting. Published `node-telegram-api@1.0.1`, feel free to re-open if the issue still persists. :grin:
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi mdibaiee,
I've noticed that packaged npm module version 1.0.0 does not contain up-to-date code changes from my recent PR. Has the build process actually taken the latest code? Because when I look at downloaded module built source code it seems it's transpiled against an older source code.
Woops, sorry, you are right, I didn't run
gruntbefore deploying the latest version, thanks for noting. Publishednode-telegram-api@1.0.1, feel free to re-open if the issue still persists. 😁Nice! Just pulled the 1.0.1, all good now. Thanks once again! :)