[WIP] Update route-recognizer.

[nathanhammond]

Do not merge.

This is the complete enumeration of tasks gating landing of what will be the next version of route-recognizer into Ember. I'm hoping to land this as part of 2.9.

• Port build into ember-route-recognizer.
• Port benchmarks into ember-route-recognizer.
• Add warning for duplicate route addition.
• ES3-ify dist/*.
• Performance
  • Ensure benchmarks are approximately the same speed or better.
  • Convert to TypeScript
  • Do a better job at serialization (breadth-first compaction).
• Improve the automatic serialization build process.
  • Make it less brittle.
  • Make the addon version's build process strip out the compiled-in route-recognizer when used with older versions of Ember.
• Testing
  • End-to-end Ember tests.
  • More obnoxious permutations.
  • Add node-tests for the build process.
• Implement RFC #154
  • Optional Segments
  • Dynamic Segment Constraints
• Add support for this.delegate. Originally added here.
• Optimize out unreachable routes alerts user.
• Repository shuffling?
  • Move the code in ember-route-recognizer into route-recognizer?
  • Move into the emberjs GitHub org.

[homu]

☔ The latest upstream changes (presumably #14058) made this pull request unmergeable. Please resolve the merge conflicts.

[rwjblue]

@nathanhammond - This is still on your radar (just delayed), right?

[nathanhammond]

Not only on my radar, still making progress: https://github.com/nathanhammond/ember-route-recognizer/commits/master

On 11/5 I built a 100% working copy of Ember with my route-recognizer fork. Need to write high quality benchmarks that can be run in different modes (clean visit, Fastboot with pre-built-route table, etc.) before proceeding with the perf work.

[marcemira]

👋 @nathanhammond - Just wanted to know if this still going to happen. Thanks 🙏

[mmun]

Closing as stale. (Route recognizer is already at version 0.3.3).