🚨 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 📦🚀

Maybe for next few (1-2) year due of author busy

Hi users & stargazers!

I'd love to hear your ideas and agreements.
Also, for this feature (drop-in replacement), i am need two or three developer with free time and/or support for development hours (contact me for more information at [email protected]).

I am think this idea like nanoexpress Pro which is differs by performance, features and support.
If you like that, please leave "Emoji 👍".

Below you can see at which cost what you can get

Simple

• Free
• 4-5x faster than Express (not in all-cases)
• 2-3x faster than Express (for Async routes)
• Validation/Serialization out-of-the-box
• Express.Static-like method
• Auto Swagger/OpenAPI documentation
• Latest Dependencies
• Apache Licensed

Pro

• Starting from 25$/month per user (only npm accessing) or 50$/month (access to project private repo)
• 6-7x faster than Express (in most-cases)
• 4-5x faster than Express (for Async routes)
• Lighter size
• More polyfilled methods
• Express.Route polyfill
• Express.Static polyfill
• Less bugs and errors
• Much Stable Performance / RPS
• Auto Swagger/OpenAPI documentation
• Bug-Fixes within 4-8 hours (if you paid for Pro)
• Latest dependencies
• Commercial license (license will be valid until you stop paying) for closed-source project per person, ONE person can use this if purchased, other can't if other not purchased.

Note: If you not agree, i will continue support this project.
Thank you.
I hope you understand me.

Update 1: You can try PRO in your open-source application
Update 2: Changing plans
Update 3: Update
Update 4: Change Commercial license term and remove support hour (who applied already until 19 August 2019 18:50:00 GMT+5, support hours will be applied for your purchased period of license)
Update 5: Typo fix
Update 6: Update
Update 7: Price improvement
Update 8: Price was changed, see my Patreon page

use middlewares

import nanoexpress from '@nanoexpress/pro-slim';

function two(req, res, next) {
    req.two = true;
    next();
}
  
const app = nanoexpress();
app.use(two)  

app.get('/', async () => {
    return ({ status: 'ok' });
});

app.listen(3000);

Error:Only Async Functions are allowed to expose route