Koen Punt

Verbose logging from the test environment: ``` [StripeTerminal] m Stripe trace identifier: retrievePaymentIntent!175740733900001714641423523 [StripeTerminal] s scope=SCPTerminal event=retrievePaymentIntent_start command=retrievePaymentIntent [StripeTerminal] t scope=SCPAPIRequest event=api_request_get api_endpoint=payment_intents.pi_3PBaSGKo27ACZLjH0vdTjQkZ [StripeTerminal] t scope=SCPAPIRequest event=api_response_success api_endpoint=payment_intents.pi_3PBaSGKo27ACZLjH0vdTjQkZ http_method=GET http_status_code=200...

An additional test to monitor certificate validity couldn't hurt either 😃 See: #240

@jchli you could use our fork if you like: https://github.com/justacodename/deployment-status

> Majority of Rails applications Not so sure about that..

I've released a [new version to npm](https://www.npmjs.com/package/node-sass-asset-functions) that replaces `node-sass` with `sass` (Dart Sass). Development will continue in this fork: https://github.com/koenpunt/node-sass-asset-functions

I appreciate the effort, but there's really too much going in this PR; formatting, code style, more modern javascript language constructs, etc. The code formatting for example is probably based...

I've released a [new version to npm](https://www.npmjs.com/package/node-sass-asset-functions) that replaces `node-sass` with `sass` (Dart Sass). Development will continue in this fork: https://github.com/koenpunt/node-sass-asset-functions

This maybe can be achieved by making `node-sass` an [optional dependency](https://docs.npmjs.com/files/package.json#optionaldependencies).

If you can setup a test which demonstrates that relative paths are not working, that would be great!

Didn’t know about this usage. Can you add tests for this? Also follow the current code style (e.g. semicolons)