The CLI does not take the custom folders into account.

[bfovez]

Lots of imports like this in the installed code:
import { ... } from '$lib/datagrid/...'
import { ... } from '$lib/datagrid-enhanced/...'
even if the CLI was told other folders than the default ones (/src/lib/datagrid and /src/lib/datagrid-enhanced).

Worse, lots of imports like this (double-dotted) :
import { ... } from "../../../datagrid/plugins/...".
This pattern ruins the custom 'datagrid-enhanced' folder if we chose, say ".src/lib/components/datagrid/enhanced".

It would probably better to stick with this pattern (using $lib):
$lib/<datagrid-enhanced-custom-folder>/...
throughout the code base, in a coherent manner.

[tzezar]

That last option seems to be the best—I completely agree with you! Keeping everything consistent with the $lib/<datagrid-enhanced-custom-folder>/... pattern makes a lot of sense and will help avoid issues with deep relative imports. I’ll start working on this after the weekend. Thanks for the feedback, I appreciate it!

[tzezar]

Hey everyone — first off, sorry for the long delay! I've been caught up with some personal stuff, but I finally have some spare time and will be actively working on the project again.

The upcoming changes are quite significant and will be released as v3 of the datagrid. This will also align with the latest Tailwind update, so it’s a good time for a clean break and some architectural improvements.

One thing I wanted to bring up: the current state of imports is admittedly messy — a mix of hardcoded relative paths like:

import { ... } from "../../../datagrid/plugins/...";

and some inconsistent $lib/... usage. These patterns don't hold up well with custom folder setups (e.g. src/lib/components/datagrid/enhanced), and I'd really like to fix that in v3.

What do you all think about fully adopting Vite path aliases for all internal imports instead? For example:

import { ... } from "@datagrid-enhanced/plugins/...";

We could allow configuring these in tsconfig.json/vite.config.ts, making the whole thing more flexible and readable across setups — instead of hardcoding $lib/ or using relative paths.

Curious to hear your thoughts!

— Tzezar