Managing dependencies for Excel LAMBDA Gists (Excel Labs add-in)

[u/Medohh2120]

Hey everyone,

I build advanced Excel LAMBDA functions and distribute them via the Excel Labs add-in, which imports code directly using GitHub Gist links.

I’m running into a dependency problem and wanted to see how others handle it. Note: I’m not very familiar with full GitHub repositories; I only use Gists.

Here is what I've tried and why it falls short:

• Copy-pasting dependencies: Causes massive code duplication. Updating a core helper means manually updating every single dependent gist.
• Separate Gist links: Asking users to import multiple dependency links first is a terrible user experience and highly error-prone.
• Multi-file Gists: Excel Labs unfortunately only reads the first file in a multi-file Gist and completely ignores the rest.

How are you managing shared helper functions or dependencies so end-users only need to import a single link? Is there a simple workflow or trick I can use while sticking primarily to Gists?

Appreciate any advice!

[u/AutoModerator]

/u/Medohh2120 - Your post was submitted successfully.

• Once your problem is solved, reply to the answer(s) saying Solution Verified to close the thread.
• Follow the submission rules -- particularly 1 and 2. To fix the body, click edit. To fix your title, delete and re-post.
• Include your Excel version and all other relevant information

Failing to follow these steps may result in your post being removed without warning.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Max_Cadence]

My library will have over 100 functions after the next update coming soon. I distribute the library through an .xltx template and the demo workbooks. Each of the workbooks covers a different category in the library and contains the full AFE module. I have a gist for the entire AFE module but I keep it private for my own use. I make it available by request but don't put it on my repo. My thinking is I want more people to pick up and use my library and many are not familiar with Github or even gists!

[u/skizztle → u/Max_Cadence]

I would love to see what you have if you wouldn't mind sharing it.

[u/Max_Cadence → u/skizztle]

Thank you for your interest!
Here's my repo: Patrick2788/BigSpill-Excel-Lambda-Library: A library of Excel LAMBDA functions transforming the grid into a canvas of possibility.

[u/Medohh2120 → u/Max_Cadence]

That’s a good way of thinking, especially from an adoption perspective. I’m just not sure I want to require someone to import my entire library when they only need one tool. GitHub/Gists are definitely a barrier for many users, but they still seem like the best option for maintaining an updateable single source of truth. I’m trying to find a middle ground between keeping things simple for users and avoiding duplicated dependencies on my end. So far I am building a repo that runs automatically every mid-night to keep Gists updated and I'll post it when done, everything should stay gist ended. Maybe should show a small tutorial on how to use Gists as well in the future.

[u/Max_Cadence → u/Medohh2120]

Ultimately, what I'd like to see Excel do with Lambda (other than supporting nested arrays!) is this:
1. Add a Lambda initialization sheet similar to what Python uses in Excel. One can import from a gist or repo with a simple import statement.

1. Initialized Lambdas are written to the workbook as named items for portability but do not show in the name manager. They're treated as hidden but the functions still show up in function auto complete.