Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
RFC: `hydrate.copy` API
See original GitHub issueThis issue is for collecting feedback on the hydrate.copy API, currently experimental as of Architect 10.5.
The goal of the hydrate.copy API is to give Architect plugin developers a hook for copying arbitrary files and folders into all Lambdas after dependency and shared code operations are complete, thus ensuring that such filesystem mutations will be present in deployment.
For more information about the API, please refer to the docs, as well as the Arc 10 API RFC. We’d love to hear what you think here about hydrate.copy (and other hydrate.* API ideas) here!
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hmm, clever idea. I had also been thinking of the opposite: ONLY share to a given Lambda.
I’m thinking that at least just to start (and since this API is still in beta) how about we change it to hydrate all Lambdas, regardless of shared code. And if folks want this to be more filtered we can hear that feedback and add filtering features.
Here’s a PR, lmk what you think: https://github.com/architect/hydrate/pull/163
The above changes are now out in Hydrate 3.1.5 / Arc 10.7.3!