Skip to content
Steven Levithan edited this page Feb 22, 2016 · 195 revisions

See version history for released versions.

XRegExp 3.1.0-dev: completed changes

The following changes have been completed and are available via the latest build here on GitHub:

  • Fine tuning: require('xregexp').XRegExp is no longer supported--XRegExp is exported directly so there's no need to access it via a property. Use require('xregexp') instead. In v3.0.0, both options were supported.
  • Fix: Fixed AMD detection when used in Firefox addons. [chocolateboy] (#113)
  • Fix: (?:)* is no longer a syntax error. [Johannes Fahrenkrug] (#112)
  • Fix: In XRegExp.build subpatterns, don't treat $ as trailing when followed by an escaped symbol.
  • Fix: Fixed an edge case XRegExp.build bug when used with flag n, mixed named and unnamed captures, and named backreferences. (#68)
  • Other: Marked use of XRegExp.install('natives') as deprecated. Support for overriding native methods will be removed in the next major release.
  • Other: Added a bower.json config. [Tomas Cassidy] (#91)
  • Other: Updated the package to use CommonJS and Browserify for the build. This makes the XRegExp package a proper citizen on the npm infrastructure while maintaining xregexp-all.js compatibility. [Alex Gorbatchev] (#122)

Share your ideas

Open a new issue here on GitHub, or fork the repo and start hacking.

Clone this wiki locally