* Fix codeFrame formatting
Pushing the codeFrame first results in ugly line breaks or extra spaces.
* Include cause in MODULE_FAILURE message
The error is always a wrapper for an underlying cause so it should be easier to determine what caused it.
* Add a codeFrame for failed _install
We normally only want this in dev mode but service CRUD should always provide detailed info.
* Expose codeFrame in Foxx CRUD
The codeFrame can only come from a failed _install, so let's make it visible to Foxx CLI and friends.
* Add codeFrame to runScript
Scripts can also only be executed with access to the Foxx API so we can provide the same info as during CRUD.
* Trim codeFrame fileName to basePath
If we have a basePath, we don't need to expose the full path to the user for the codeFrame to be meaningful.
* Fix getReadableName
Previously 'catch-fire' would become 'Catch Ire'.
* Add to changelog
* Improve Foxx cluster resilience
Fixes#2083Fixes#2384Fixes#2408
Addresses #1892
* Port old Foxx API
* Implement single-file services
* Add console.errorStack/warnStack/infoStack helpers
* Simplify serviceInfo validation
* Extract github/upload logic into Aardvark and old FM API
* Move generator logic into Aardvark
* Move zip/js buffer logic into FM core
* Add Foxxmanager tests
* Send empty response when no README
* Disambiguate script arg format
Historically we allow passing an array of positional arguments or an arbitrary first argument.
This is surprising behaviour, so we should just always treat the value as a first argument.
* Rebuild bundle in development mode
* Nicer HTTP docs formatting
* Create Foxx HTTP docs
* Simplify service upload handling
* Remove inline swagger docs
* Implement public download route
* Consistency
* Rebuild aardvark
* Move bundle route into /_api/foxx/_local
* Rebuild Swagger API docs
* Add changes to CHANGELOG
* More docs
Don't clutter stacktraces for Node compatibility at all. Just add lineNumber/columnNumber/fileName to the object.
These are non-standard but there is precedent for these names in Mozilla.
Clobber stacktrace instead of wrapping in another exception with wonky message string.
This makes SyntaxError details node-compatible and parseable for generating code frames.
Alan Plum
Andreas Streichardt