regex
intl-proxy
| regex | intl-proxy | |
|---|---|---|
| 1 | 2 | |
| 33 | 4 | |
| - | - | |
| - | 4.1 | |
| over 1 year ago | 5 months ago | |
| Elm | Elm | |
| BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
regex
-
Learning Elm by porting a medium-sized web front end from React (2019)
https://github.com/elm/regex/commits/1.0.0/
So it seems like by the time of the official release you could have replaced your five lines with `Regex.fromString`.
But the missing Intl API is definitely a huge pain, and I understand that you were switching away if you needed it extensively. Or expected to want other sync APIs wrapped.
A common way to solve something like this is with proxy objects like in https://github.com/anmolitor/intl-proxy but it does not give access to every feature in a nice way.
I went the route of least resistance and built the Elm compiler without the Kernel code check. But in the past few years I hardly needed that anymore.
intl-proxy
-
Learning Elm by porting a medium-sized web front end from React (2019)
Yes, ports or custom elements are the recommended options, https://github.com/elm-community/js-integration-examples
There are a bunch of other options/workarounds/hacks depending on the need. E.g. using getters or creating proxy objects https://github.com/anmolitor/intl-proxy, or event listeners, or postprocessing of the generated JS code, but those shouldn't be the first idea to reach for.