URI as primitive in @lix-js/fs

[felixhaeberle]

Problem

We often have to deal with paths inside multi env code like the new cross-sell packages which aim to simpify the cross-sell of our apps with access to the fs.

The operations done on the fs often requires path manipulation and therefore we introduced normalizePath & normalPath – both of them are poorly executed because no higher approach has yet been found to tackle paths multi env (node/web etc.)

Proposal

Come up with a solution like

import path from "@lix-js/path"

// use it in nodejs
path.join()

// use it on the web
path.join()

I'm surely only scratching the surface here, but the bugs in opral/monorepo#2184 alike seems that there is an urge to introduce @lix-js/path.

[samuelstroschein]

@felixhaeberle

1. This will most likely be included in the upcoming @opral/lix fs.

import { URI, fs } from "@lix-js/fs" 

URI.join()

2. We need URI's, not paths since we are dealing with network "paths", local paths, and more

[felixhaeberle]

yes! I see the need for URIs also/instead

---

this "path" proposal should be envolved to what we actually need but the current state of packages/apps have to

function joinPath(...parts: string[]): string {
	return parts.map((part) => part.replace(/\/$/, "")).join("/")
}

& a weird mix of packages using normalPath & normalizePath

is 🥴

---

TLDR: @samuelstroschein feel free to rephrase the proposal

[janfjohannes]

@felixhaeberle good to have this as a ticket, this will be much less work as
a) we have unix path normalization so lix fs will only have / path delimiters, not
b) lix will have scped paths to the repo and can be further scoped down to replace the current "withAbsolutePaths" wrapper, which will remove the need for many cases where relative paths are used

in the end there should be not much need for helper funcitons except for something like path.resolve for some cases.

[samuelstroschein]

https://linear.app/opral/issue/LIX-29/uri-as-primitive-in-lix-jsfs

[linear]

LIX-34 `URI` as primitive in `@lix-js/fs`

[samuelstroschein]

@felix.haeberle here you go