Deployer is a great tool for PageBuilder deployments, however there are some issues that could help the developer if they are fixed:
Errors displayed in the screen when a bundle fails to deploy don't give the developer enough information. The errors are just a sentence like "npm exit code 1" when you have a problem in your bundle, and that's it, you need to go to the logs or start investigating the problem by yourself. Also the "ETIMEOUT" error is pretty underwhelming.
NPM version currently supported is 6. If you are using NPM version > 7 to create your package.json, the deployer will execute NPM version 6 and the dependency tree generated by a higher version is more complex. The result is a performance reduction of the NPM installation process during deployment that usually generates a ETIMEOUT error.
David del Pino
Hi David,
We have shipped a deployer capability allowing developers to access build logs in failed and timed out builds. You can see the updated deployer documentation here: https://redirector.arcpublishing.com/alc/arc-products/pagebuilder/fusion/developer-documentation/deploying-a-feature-pack/ that talks about the new feature under "Debugging and Troubleshooting Failed and Timed out Builds" section.
As far as npm versions, since Engine runs on specific lambda nodejs runtimes, we are suggesting to use specific npm version for each engine version that runs on the corresponding nodejs runtime in lambda. They are documented in the Engine limits and requirements doc in ALC.
Hi David,
Thanks for sharing the detailed feedback about your deployment experience. This is definitely something we're considering in our upcoming releases.