If user tracking fails to connect, slicemachine fails and is unusable

Versions

• slice-machine-ui: 0.4.2
• node: 16.10.0

Reproduction

When using DNS ad-blocking, slicemachine dies when invoked in develop mode and the page is loaded

Additional Details

Console error:

[slice-machine] AxiosError: connect ECONNREFUSED 0.0.0.0:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1146:16) {
...
_currentUrl: 'https://....D6P:@api.segment.io/v1/batch',

I’ve obscured the API key for segment.io -> Twilio tracking

Steps to reproduce

Enable pi-hole, a DNS ad blocker or point api.segment.io to an invalid IP or localhost

What is expected?

Customer tracking should be optional and not mandatory for the slice machine to work

What is actually happening?

Slicemachine closes when the local page is loaded

[lachieh]

@ReeceM that works! Thanks!

For posterity, the command is: npx @slicemachine/init script --tracking false

It would still be good to fix the underlying issue, and I’d be willing to assist with it if PRs are accepted.

[ReeceM]

@lachieh https://github.com/prismicio/slice-machine/issues/466#issuecomment-1136124618

/cc @comeprismic if this is still correct?