Some questions about using this in production

[Evertt]

Well first of all, is this project still maintained? Because I see that the last commit was 4 years ago.

Secondly, is it possible to use this in production and configure it to log to some external service (e.g. Sentry) and only send the log maybe when some error has occurred? Maybe as part of the stack trace if that's possible?

Thirdly, is it possible to use minify in production but to then use source maps in order to still figure out what the correct filename, line number, and maybe even variable names in the expression would have been in the original source code?

[parker-crabnebula]

Hey @Evertt!

No, this isn't maintained anymore. It should still work, but the scope was quite small so it hasn't needed any updates.

I think extending it to log to an error service is outside of the scope of this project. Many of these error capturing services will show you the history of console usage though, so perhaps you don't even need to configure this yourself..

On the topic of minification - unfortunately it obfuscates the output to the point where it's not very useful anymore to this package. Source maps are handy, but are not a part of the scope of this project either. Even if we were to pull from source maps, we wouldn't get the variable names back out, and it requires reading files from disk which could increase security risk, hence why I said it was out of scope.

---

Remember that you have the power to fork and build your own, or if we discuss something and determine it to be in scope you could submit a PR here. :)