We are encountering challenges while testing new adaptor changes on the Lightning platform because the adapter must first be released on npm before it can be pulled into the Lightning environment. This creates a bottleneck in the development workflow, leading to delays and inefficiencies in testing and validation.
Support for this has been added to the Worker. We just need Lightning to catch up now
@mtuchi this has been fixed in Use local adaptors in a local Lightning instance · Issue #905 · OpenFn/lightning · GitHub. Please upgrade to v2.10.15.
cc: @joe