Repository navigation
process is not defined when used in Vanilla JS (without Node.js) #6078
Description
TanStack Table version
v8.21.3
Framework/Library version
vanilla (through Rails importmap)
Describe the bug and the steps to reproduce it
I'm using @tan-stack/table-core in vanilla JS without any bundler or Node.js runtime. It seems that createTable() function checks runtime environment for debugging, which throw an exception for my setup.
const M = [t, c, s, a, n, l, p, m, F, r, f, C, h, S, g];
function createTable(e) {
var t, n;
process.env.NODE_ENV !== "production" && (e.debugAll || e.debugTable) && console.info("Creating Table Instance...");
I temporarily use a mock process object to workaround. Would it be nicer to check process at first?
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
(no need)
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
Yes, I think I know how to fix it and will discuss it in the comments of this issue
Terms & Code of Conduct
- I agree to follow this project's Code of Conduct
- I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
Activity
BranLiang commentedon Nov 12, 2025
Got the same error, here is the solution I made to bypass that.
bin/importmap pin @tanstack/table-coreIn the umd build, there is no process env check.
fix(table-core): guard process.env checks for non-bundled environments
isaackaara commentedon Mar 4, 2026
Opened #6185 with a fix for this. The issue is that the ESM build output preserves raw
process.env.NODE_ENVreferences, which throw in environments without Node.js globals. The fix introduces a safeisDev()utility that checks for the existence ofprocessbefore accessing it.fix(table-core): use the bare NODE_ENV check for the range filter war…