fix(table-core): Avoid process not defined in environments not setting a process variable

[timrittgers]

When running the library in an environment that is not setting the process variable, the library throws a not defined error and breaks the render. This change checks to see if the variable exists before attempting to read it to avoid this.

[KevinVandy]

What environments do that?

[timrittgers]

What environments do that?

I have a situation where we are bundling Tanstack into a library component, then distributing the component as a standalone package that can be loaded directly in an html page. In this scenario, there is no process variable defined and the tanstack library fails.

[KevinVandy]

Are you sure that you're not accidentally importing from src instead of the proper build output?

Also, maybe try importing from the umd output, which does not have any process.env in its output

[timrittgers]

Are you sure that you're not accidentally importing from src instead of the proper build output?

Also, maybe try importing from the umd output, which does not have any process.env in its output

I'm importing the Tanstack library into my project's component like this:

import {
  Cell,
  ColumnDef,
  ColumnSort,
  createColumnHelper,
  getCoreRowModel,
  getFilteredRowModel,
  getPaginationRowModel,
  getSortedRowModel,
  Header,
  PaginationState,
  RowModel,
  Table,
  TableOptions,
  TableState,
} from '@tanstack/table-core';

There wouldn't be a way to just import the pieces I need using the umd, would there?

I'm also curious what the harm would be in detecting the process variable in the library before calling it?

[KevinVandy]

I'm also curious what the harm would be in detecting the process variable in the library before calling it?

I have just never seen any other NPM library ever have to do this, so I think there should be a better way.