Browser-ready dist/ folder?

[chriscalo]

Any chance I can convince you to publish a browser-ready dist/ folder to npm? That makes it possible to use your library without a build step via unpkg.com, for example:

<script src="https://unpkg.com/regexr@1.3.0/dist/regexr.js"></script>

[trusktr]

@chriscalo Hello! Sounds good.

I do that with my latest libs, but at the time I didn't have the build setup that I share with my newer packages.

In the meantime, something like the following should work (haven't tested it):

<script>
  var module = { exports: {} }
  var exports = module.exports
</script>
<script src="https://unpkg.com/regexr@1.3.0/regexr.js"></script>

then r (or regexr) will be available as a global.

[trusktr]

Alright, done! Try the following:

<script src="https://unpkg.com/regexr@1.4.3/global.js"></script>
<script>
  const r = regexr.default // grab the default export from the global
  console.log(r`/foo/` instanceof RegExp) // true
</script>

[trusktr]

Hmmm, wait, something didn't work as expected when I tested locally.

[trusktr]

Alright fixed it in v1.4.4. Try:

<script src="https://unpkg.com/regexr@1.4.4/global.js"></script>
<script>
  const r = regexr.default // grab the default export from the global
  console.log(r`/foo/` instanceof RegExp)
</script>

[chriscalo]

Working for me. Thanks, @trusktr 🙏