Express gateway crashing due to invalid code in rewrite plugin dependency about express-gateway-plugin-rewrite

[DrMegavolt]

can you provide config example?
from what I see in line 13 in stack trace
const compiledExp = pathToRegExp.compile(actionParams.rewrite);
it looks like no rewrite property

rewrite:
      -
        action:
          rewrite: /status/:code

[XVincentX]

Note:
Once the schema support in the gateway will be published, I'll definitely make a PR and add a schema for the parameters so this should not happen anymore.

[XVincentX]

@imthinhvu Did you solve your issue?

[chronicIntrovert]

@XVincentX I did not. I ended up giving up on express-gateway for now as I didn't want to deal with not knowing the file configuration specifics, and I don't have the time to dig into issues like this to figure it out.

[XVincentX]

That's sad to hear — I'd love to know more about that. Did you find the documentation hard to navigate? Or is the configuration file just hard to reason about?

I'm going to close this one for now — feel free to reopen if you'd like to dig into this again!

[chronicIntrovert]

@XVincentX For the most part, the documentation is pretty easy to navigate--I did not have a bad experience going through the initial "Getting Started" steps. I did find some difficulty around the configuration with plugins, however, and think there can be some work done there. I have no doubt that your suggested fix would have fixed my problem, but I also would've expected a simple fix like that to error out properly to the user. Express-Gateway seems like a great product, but as of right now, in my opinion, it's just not mature enough to try to use in an enterprise setting. I will definitely try revisiting it again in the near future. Thanks for all of the hard work!

[XVincentX]

I totally get your concerns — and one more time thank you for taking the time for filing the issue.

About this one in particular, the upcoming gateway releases will have a schema validation feature that should hopefully totally prevent these problems in the future. We try to improve as we go, and offer the best support we can.

It's just not mature enough to try to use in an enterprise setting

That's a fair point. What's sure is that we do not really have super enterprise on our "curriculum" yet — although Joyent is actively using us and giving great feedbacks.

I hope you're going to come back one of those days — and see you happy!