Closed George-Payne closed 1 week ago
Latest commit: 318cdd5517a0854e0d6395e301a6a0154b8f5912
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
Name | Link |
---|---|
Latest commit | 318cdd5517a0854e0d6395e301a6a0154b8f5912 |
Latest deploy log | https://app.netlify.com/sites/car-park-attendant-cleat-11576/deploys/667affc117bae900088db6a3 |
Deploy Preview | https://deploy-preview-8267--car-park-attendant-cleat-11576.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
When using a custom publish provider, it is first attempted to be imported from the build resources, then if that fails, it attempts to import it from node_modules.
Currently, if the first attempted path fails, it logs the error to the console.
This happens multiple times per publish, and adds a lot of noise to the output.
Considering it's a (possibly) expected error, it would be better to move this to a debug log, with explanation.