Mastodawn

I made a contribution to browserslist:

https://github.com/browserslist/browserslist/pull/819

I have been trying to get the Lume static site generator to run inside a #Dropserver sandbox, but I have been running into all kinds of issues: some modules written for #NodeJS assume they have read permissions for the entire disk, and error out when you run them with restrictive permissions. Any project that uses #PostCSS + #autoprefixer (ie most build systems) will hit this.

https://github.com/browserslist/browserslist/issues/813

1/2

feat: add BROWSERSLIST_ROOT_PATH by teleclimber · Pull Request #819 · browserslist/browserslist

check that loc is inside BROWSERSLIST_ROOT_PATH in eachParent add tests update Readme fixes #813

GitHub

Show thread

Olivier Forget Feb 14, 2024

So I proposed and implemented this change but it doesn't immediately solve the problem for Dropserver since I don't allow setting environment variables, and I'm not sure I should. It's fraught with possible problems.

It's possible running builders in a Dropserver sandbox will not work. These scripts are very liberal about reading stuff all over your disk. Some want read access to random things, and they're not even critical to the function, yet error if you deny access.

2/3

Show thread

Olivier Forget Feb 14, 2024

My goal is a Dropserver demo app that has an interface for writing blog posts, and a "generate site" button that runs Lume and creates a static site. The site is served by Dropserver's static site routes (no sandbox involved).

It's been a roller coaster, but I'll keep hacking at it. I already made the appspace dir the current working directory. That was an obviously good thing to do and it helps many npm scripts.

https://github.com/teleclimber/Dropserver/commit/cec55747bfd981d30225fbad9f419f99324f81b2

3/3

feat(ds-host): make appspace files dir the cwd of sandbox · teleclimber/Dropserver@cec5574

- add testfixtures for app and appspace files in sandbox package - fixes #120

GitHub