Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move middleware to their own projects #79

Open
CodisRedding opened this issue Oct 22, 2016 · 3 comments
Open

move middleware to their own projects #79

CodisRedding opened this issue Oct 22, 2016 · 3 comments

Comments

@CodisRedding
Copy link
Contributor

I'd be happy to start moving the remaining built-in middleware functions to their own projects and add links from readme since some of these are not mentioned. Let me know what you think.

correlate
json
logger
messageDomain
package

@borela
Copy link

borela commented Nov 16, 2016

It would be interesting to have separate npm packages for the middlewares but still have a monorepo as it would be easier to find breaking changes or bugs. An example of that is babel.

@mateodelnorte
Copy link
Owner

I'm all for it. This will have to be part of a larger, breaking set of changes we'll need to start off at 3.0.0.

Happy to start working on this and other large changes on a new 3.0.0-pre branch. That work for you?

@patrickleet
Copy link
Collaborator

There is now a servicebus org for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants