@Durgesh Shekhawat joined #community-contributors. They’re also new to Lightdash Community.

Hi Lightdash community! 👋 I'm Durgesh Shekhawat, a full stack developer from India. A bit about me — I independently built and deployed joincodershub.com, a developer networking platform using React, Node.js, Express, and MongoDB on AWS EC2, featuring real-time chat, payment integration, and email automation. The platform crossed 35,660+ requests in just 30 days with users from 5 countries 🚀 I came across Lightdash recently and was genuinely impressed by what you're building — self-serve BI on top of dbt is a brilliant idea and the codebase looks really well structured. I noticed that PR reviews from outside contributors are paused for now — totally understand, small teams move fast! I'm happy to wait until it reopens and would love to contribute when the time is right. I'll keep an eye out for when the

open-contribution

label comes back. Looking forward to being part of this community! 🙌

@Prathmesh Waghmare joined #community-contributors. They’re also new to Lightdash Community.

Hey guys, Hi :) do we have contributions open right now ?

I would like to contribute to the org

@Yasuhiro Arakaki joined #community-contributors. They’re also new to Lightdash Community.

Hi Lightdash community! I'd like to contribute to Lightdash. I tried to follow the contribution steps, but the Slack invite link in CONTRIBUTING.md was expired at the time — it was just fixed in a6c3b71. So I went ahead and created the issue and PR before joining here. Apologies for the out-of-order process. - Issue: https://github.com/lightdash/lightdash/issues/21142 - PR: https://github.com/lightdash/lightdash/pull/21143 It adds native PDF export for scheduled deliveries using the existing headless browser infrastructure —

page.pdf()

alongside the existing screenshot path. The PDF has selectable text, clickable links, and matches the dashboard layout exactly. Happy to discuss the approach or make any changes needed.

Hi! I just opened an issue for a CJK font rendering bug in scheduled deliveries and screenshots: https://github.com/lightdash/lightdash/issues/21499 Japanese text renders with a Chinese font (WenQuanYi Zen Hei) instead of Noto Sans CJK JP in the headless browser container. The fix is a one-line CSS change — adding

'Noto Sans CJK JP'

to the font-family stack in

mantineTheme.ts

. I've verified it locally and would like to work on the PR. 🙋

@Dhruvan joined #community-contributors. They’re also new to Lightdash Community.

⚠️ Important security update for Lightdash CLI users Earlier today a widely-used open source package (

axios

) was briefly compromised on npm. This affected the Lightdash CLI since Lightdash depends on

axios

. Most people are unlikely to be affected. You're only affected if a fresh install of the CLI (

npm install -g @lightdash/cli

) happened between midnight and 3:30am UTC today (March 31). This would most commonly be a CI pipeline, a Docker build, or a manual

npm install

. If you installed the CLI before today and haven't reinstalled, you're fine. What to do: → Update to

@lightdash/cli@0.2695.1

- this pins the dependency to a safe version → If you did install during that window, please reach out to us directly and we'll help you check Lightdash Cloud is not affected. Full details for anyone who wants them: https://github.com/lightdash/lightdash/security/advisories Happy to answer any questions here

I opened an issue about adding a non-root

USER

to the production Dockerfile: https://github.com/lightdash/lightdash/issues/20322 Currently the

prod

stage doesn't set a

USER

directive, so the container runs as root by default. This is a security concern — if a vulnerability is exploited, an attacker could gain root-level access to the container. Docker's best practices also recommend running as a non-root user: https://docs.docker.com/build/building/best-practices/#user I'd like to contribute a PR for this. Before I start, a few questions: - Is this something the team would welcome as a contribution? (I see it's tracked as PROD-3033) - Should this be treated as a breaking change? Users who mount host volumes may hit permission issues after this change. - Any preference on UID/GID values or approach? Happy to align on the approach first before writing any code. Thanks!

I've submitted a PR to fix the CORS issue reported in #17452: https://github.com/lightdash/lightdash/pull/21949

I found a bug in the PDF-only scheduled delivery feature that I added in #21457. When using the PDF format, charts rendered with ECharts (Canvas) are intermittently blank in the generated PDF — tile titles and borders appear, but the chart areas are empty. The IMAGE+PDF path is stable because

page.screenshot()

is called before

page.pdf()

, which forces the browser to fully paint all canvas elements. The PDF-only path calls

page.pdf()

directly, and Chromium's print rendering pipeline unreliably captures canvas content. I've filed an issue with the root cause analysis: #21950

I've submitted a PR to add a new endpoint for download activity endpoint and it is not assigned an issue: https://github.com/lightdash/lightdash/pull/22879

Hey team, I had a small change related to database migration validation I wanted to push up steam. Let me know if you have any suggestions or concerns: https://github.com/lightdash/lightdash/pull/23035

@Milan Padhariya joined #community-contributors. They’re also new to Lightdash Community.

@Tarunswamy Muralidharan joined #community-contributors. They’re also new to Lightdash Community.

Hi team! 👋 I'm running Lightdash self-hosted on BigQuery. Just wondering about the status of #19636 — I originally reported this on v0.1999.0, and it's still reproducible on v0.27741.0. I have a local fix and would love to contribute it as a PR if that works. Any chance of getting an open-contribution label on this?

Hey Lightdash team, Giacomo here! 👋🇮🇹 I'm a Data Analyst at FINN, where we use Fivetran, BigQuery, dbt, Looker and recently also OpenClaw via Slack (users love it!). Using Looker, I discovered how beneficial it is when the semantic relationships between tables is tightly coupled with the visualisation layer, and how easy it is to edit/maintain these relationships in code with the advent of LLM coding tools: something that Lighdash nails perfectly, unlike other open source alternatives. While exploring how to recreate an open source equivalent of our data stack, I found out: • BigQuery -> DuckLake • Fivetran -> dlt • Looker -> Lightdash (but it does not support DuckLake yet) This brings me to opening an issue and submitting a pull request to add DuckLake support. If you see value in adding support for this lakehouse format, could you assign the

open-contribution

label to the issue and review the pull request? I'm happy to reshape it as needed and address any question you may have. Thank you and have a great day!

Hey @everyone I want to contribute in the LightDash . are contribution open ? Should i take the issue and start contributing ? Need your insights , Thankyou !!

Hi team 👋 I have a feature request about the global search (the search bar you open with Cmd/Ctrl + K) that I'd love to discuss! Currently the search starts once you type 3 or more characters. That works well for English. But in Japanese — and CJK languages (Chinese, Korean) in general — short words of just 1 or 2 characters are very common, and we often want to search for them (e.g. 売上 = "sales", 表 = "table"). With the 3-character minimum, these can't be searched at all, which makes the search a bit hard to use for us. Would it be possible to start the search from 1 character when the query contains CJK characters (while keeping the 3-character minimum for the rest)? It would be my first time contributing, but I'd love to challenge myself with this one! If it sounds good to you, would you let me take this on? 🙏 (I've actually given it a quick try in my own fork already, and it seems to work fine.) Of course, if that's tricky, please feel free to just treat this as a feature request! Thanks for considering!

📣 Heads-up: Lightdash is moving to Node.js 24 — Wednesday 29 July 2026 TL;DR — most customers don't need to do anything. Lightdash Cloud and standard Docker self-hosting upgrade automatically. Anyone using the Lightdash CLI — on their local machine or in CI/CD — will need to take action. We're giving about a month's notice so you can schedule it. What's changing On Wednesday 29 July 2026, Lightdash moves to Node.js 24 (the current Active LTS). We're moving off Node.js 20, which reached end-of-life in April 2026, to stay current on security patches, performance, and long-term support. On the day, we'll also publish the exact Lightdash version that requires Node.js 24 and update our GitHub Action templates. What you need to do ☁️ Lightdash Cloud — Nothing. We manage the runtime and roll it out for you, with no downtime or action needed. 🐳 Self-hosted — standard Docker / Helm — Nothing beyond your usual upgrade. From 29 July, the Lightdash image ships with Node.js 24 built in; pull the version we announce that day and deploy as normal. 🛠️ Self-hosted — custom images, modified deployments, or building from source — Please verify your environment on Node.js 24 before 29 July. A base-image bump can pull in other toolchain updates, so it's worth checking ahead of time rather than on the day. ⌨️ Lightdash CLI users — From 29 July, the CLI will require Node.js 24, whether you run it on your local machine or in CI/CD. There's nothing you need to change before then — this notice is just so you can plan it in. When the change lands (we'll confirm the exact version that day), you'll need to be on Node.js 24: • Locally: upgrade your machine to Node.js 24 (e.g. via nvm, fnm, or nodejs.org). • In CI/CD: run your CLI steps on Node 24 — e.g. actions/setup-node with node-version: 24 (also becoming the GitHub-hosted default). If you use our GitHub Action templates, pull the latest — we'll update them for Node 24 on 29 July. • Either way, you can skip managing Node entirely with our standalone CLI binaries, which bundle their own runtime. A note on currency formatting (COP & HUF only) Node.js 24 ships updated international formatting data (ICU/CLDR). As a result, Colombian peso (COP) and Hungarian forint (HUF) amounts in server-generated exports and scheduled deliveries (CSV/Excel, emailed/Slack reports) will display without decimal places — e.g. "COP 1,235" instead of "COP 1,234.50". This matches the current international standard for these currencies and how modern browsers already display them. No other currencies or formats change. If your COP/HUF reports feed downstream automation that expects two decimals, please adjust before the upgrade. Questions? Reply to this thread — we're happy to help with CLI or self-hosting upgrades.

Data Apps just got more production-ready We’ve shipped a batch of new Data Apps improvements that make apps easier to build, connect, debug, and reuse. Here are the highlights: • Apps as code — Download, edit, version, review, and re-upload Data Apps. • External connections — Connect apps to third-party APIs through Lightdash-managed, credential-safe connections. • Query tracking and controls — Inspect the queries and external requests an app is running, then debug or save them back to Lightdash. • App visualizations — Generate reusable custom chart types with AI and use them across Explorer, saved charts, and dashboards. • Google Sheets sync — Data Apps can now open results in Google sheets, just ask for a button when building. These updates make Data Apps easier to take from prototype to something your team can trust and reuse. We can't wait to see what you build! 📚 You can read the full Data Apps docs here.

Multiple dbt projects in one Lightdash project (beta) You can now connect more than one dbt project to a single Lightdash project. If your models are spread across several dbt repos, you no longer have to choose one or maintain a workaround that stitches them together. Add each repo as a dbt source, and Lightdash merges them into a single set of explores on every deploy and preview. Your agents see the whole picture, and AI writeback opens its pull request against the repo that actually owns the model. To try it, go to Project Settings → Connection settings and find Additional dbt sources. Two things to know while this is in beta. Additional sources need to be GitHub repositories for now. And model and metric names have to be unique across your sources, so if the same name is defined in two projects the deploy will stop and tell you which ones clash. Self-hosted: upgrade to

0.3275.0

or later, then add

multi-dbt-sources

to your

LIGHTDASH_ENABLE_FEATURE_FLAGS

environment variable. This is a beta and we are actively looking for feedback. If you run dbt across multiple repos, we would love to hear how this holds up against your setup and what is missing. Reply here and we will take a look.

Hello all quick question about local/dev setup docs. CONTRIBUTING still recommends GitHub Codespaces / VS Code Remote Containers, but

.devcontainer/devcontainer.json

was removed in #5906 (Jun 2023) — that PR was about org projects API, not Docker/devcontainer. Is there a reason we intentionally dropped Dev Containers / Codespaces, or was that an accidental deletion? If unintentional, should we restore

.devcontainer

and/or update CONTRIBUTING to remove that section? Thanks

📣 Node.js 24 upgrade is live Following up on our notice from June: Lightdash has now moved to Node.js 24, starting with v1.19.0. What this means for you • ☁️ Lightdash Cloud: no action required. We manage the runtime and roll it out for you. • 🐋 Standard Docker / Helm self-hosting: upgrade to v1.19.0 or later as normal. The image includes Node.js 24. • 🛠️ Custom images or source builds: update your build and runtime environment to Node.js 24 before upgrading. • ⌨️ Lightdash CLI: v1.19.0 and later need Node.js 24 when installed via npm, both locally and in CI/CD. Upgrade Node with nvm, fnm, or nodejs.org, or skip Node management entirely with our standalone binaries, which bundle their own runtime: https://docs.lightdash.com/guides/cli/how-to-install-the-lightdash-cli • 🔧 GitHub Actions: pull the latest Lightdash CLI Action templates, which now pin Node 24. If you run the CLI directly, set

actions/setup-node

to Node 24. Reminder: COP and HUF formatting Node.js 24 ships updated ICU/CLDR data. Colombian peso and Hungarian forint amounts in server-generated exports and scheduled deliveries now display without decimal places, matching current international standards and how modern browsers already show them. No other currencies or formats change. Questions? Reply in this thread and we'll help with CLI or self-hosting upgrades.

👋 Hello, team! I’m Rohit, a full-stack developer I’m looking to start contributing to Lightdash and have been going through the repository and contribution guidelines. I’m particularly interested in frontend and full-stack contributions, and I’d like to start with an

open-contribution

issues

I'd like to work on this open-contribution issue: github.com/lightdash/lightdash/issues/27742 Since this is the only one that looks open and hasn't been assigned to anyone to work on.

Hi everyone! 👋 Thank you so much for all your contributions and for being part of this community. We’ve updated our contribution policy, so we’ll be archiving this channel. If you’d like to report a problem or suggest an improvement, please use our Bug Report or Feature Request forms. For anything else, you can reach us through your usual support channel. Thanks again for everything!

archived the channel