Wrong code published to npm
aliismael opened this issue · 3 comments
aliismael commented
Dear Colleagues,
When I run
npm install hapi-auth-cookie@7.0.0
I get code that does not look like the one on the master branch on github! I get something like this in the lib/index.js file:
'use strict';
// Load modules
const Boom = require('boom');
const Hoek = require('hoek');
const Joi = require('joi');
// Declare internals
const internals = {};
exports.register = function (server, options, next) {
server.auth.scheme('cookie', internals.implementation);
next();
};
exports.register.attributes = {
pkg: require('../package.json')
};
.....
....
....
Did someone push the wrong code base to npm?
Thanks in advance for your help.
Yours truly,
Ali
mrlannigan commented
@aliismael The code for version 7.0.0 is what was published to npm@7.0.0. I had merged a PR to upgrade this module to support hapi v17 yesterday and just a few minutes ago, cut the release to npm for 8.0.0. My apologies for the confusion.
aliismael commented
Dear Julian,
You are so kind, no need for apologies.
I am upgrading my OpenID-Connect plugin for hapi 17 as well, and I feel
what you are going through.
Thank you so much, I will keep you updated if I encounter any issue with
version 8.0.0 of your plugin.
Yours truly,,
Ali
Yours truly,
Ali Ismael, Ph.D.
Gaaiat, Inc
…On Sun, Dec 10, 2017 at 12:09 PM, Julian Lannigan ***@***.***> wrote:
@aliismael <https://github.com/aliismael> The code for version 7.0.0
<https://github.com/hapijs/hapi-auth-cookie/tree/22dfeb105705986728d5e97f4183f4d460c72608>
is what was published to ***@***.*** I had merged a PR to upgrade this
module to support hapi v17 yesterday and just a few minutes ago, cut the
release to npm for 8.0.0. My apologies for the confusion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#180 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCC3y5FHIQTL9unz8wJalPkVkIC50s6ks5s_DpsgaJpZM4Q8mTN>
.
lock commented
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.