telegram-api 1.0.0 built source code does not reflect recent PR implementing correct promise chaining #39

Closed
opened 2018-02-14 10:34:02 +00:00 by laurynas-karvelis · 2 comments
laurynas-karvelis commented 2018-02-14 10:34:02 +00:00 (Migrated from github.com)

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.

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.
mdibaiee commented 2018-02-14 10:39:57 +00:00 (Migrated from github.com)

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:
laurynas-karvelis commented 2018-02-14 10:46:57 +00:00 (Migrated from github.com)

Nice! Just pulled the 1.0.1, all good now. Thanks once again! :)

Nice! Just pulled the 1.0.1, all good now. Thanks once again! :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: thereadme/node-telegram-api#39
No description provided.