jeff-tian / egg-passport-weapp

Wechat mini program passport plugin for egg

egg-passport-weapp

Wechat miniprogram passport plugin for egg.

Example

Open https://uniheart.herokuapp.com/ to see the result.

Install

$ npm i egg-passport-weapp --save

Usage

// {app_root}/config/plugin.[t|j]s
exports.passportWeapp = {
  enable: true,
  package: "egg-passport-weapp"
};

Configuration

// {app_root}/config/config.default.[t|j]s
exports.passportWeapp = {
  key: "your oauth key",
  secret: "your oauth secret"
};

// {app_root}/app/router.js

app.passport.mount("weapp", app.config.passportWeapp);
router.get("/passport/weapp/callback", ctx => {
  // Now get you get ctx.user, write your login logic here,
  // for example, write session
  ctx.session.userId = ctx.user.id;

  // And then return something instead of redirect
  ctx.body = ctx.user;
});

see config/config.default.ts for more detail.

Example

Wechat Mini Program	Wechat Mini Program Demo version

Questions & Suggestions

Please open an issue here.

License

MIT

Test

npm run test-local

Release Notes:

egg-passport-weapp's Issues

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀