Move "try" into a dedicated project

[aurelien-reeves]

🤔 What's the problem you've observed?

The "try" as part of cucumber-expression javascript implementation oversize it and add a lot of dependency to cucumber-expression itself. It could live on its own, being inside its own repo, or within a dedicated folder within this repo

Refs. #104 (comment)

✨ Do you have a proposal for making it better?

I would put it its in own repo actually, thus it would not interfere with cucumber-expression at all

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[aslakhellesoy]

I agree! We could move it to cucumber/try-cucumber-expressions

[aslakhellesoy]

The "try" as part of cucumber-expression javascript implementation oversize it and add a lot of dependency to cucumber-expression itself.

None of the code from the try directory is included in the published npm module. Furthermore, all of the dependencies of try are devDependencies.

Nevertheless, I agree we should move it out.

[mpkorstanje]

Yes, because stuff like #112 keeps generating notifications.

[aslakhellesoy]

Done!

[mpkorstanje]

Thanks!