The goal is to bring back the old zeit now feeling: run one command in a project and get a live URL, but self-hosted.

Instead of managing Node versions or different runtimes on the server, pack.sh uses single-file executables. Build once, upload one file, run it.

This keeps server setup pretty minimal, and makes it easy to run many small apps on a cheap VPS.

Feedback welcome.

Comments URL: https://news.ycombinator.com/item?id=48195795

Points: 1

# Comments: 1

Personally, I use volta and switch between node versions in different projects, so I prefer to just use npm.

Enabling `ignore-scripts=true` protects you from almost all of the recent compromises `min-release-age=3` protects you from the rest. But you still typically need trusted dependency builds, which this script solves.

I hope that npm enables this by default in the future.

https://www.npmjs.com/package/@gkiely/safe-install

It brings a couple of protections I wanted from npm but are not built in.

Similar to Bun’s trusted dependencies, it lets you disable install scripts by default and define a list of dependencies that are allowed to run build/install scripts:

https://bun.com/docs/guides/install/trusted

It also supports blocking exotic sub-dependencies, similar to pnpm’s `blockExoticSubdeps` setting:

https://gajus.com/blog/3-pnpm-settings-to-protect-yourself-f...

I was hoping npm would eventually add something like this, but it does not seem to be happening soon, so I made a small package for it.

Comments URL: https://news.ycombinator.com/item?id=48102636

Points: 19

# Comments: 5

Pinned package versions in npm solves this.

If you want to use the latest dependencies then yes there is ongoing management required. There are tools to help with this.

Let me know your use case as I am still learning where it can provide the most value and how I should go about charging for it.

I welcome feedback on pricing/self-hosted.

Comments URL: https://news.ycombinator.com/item?id=43277784

Points: 1

# Comments: 2

1. I would replace the chairlift sequence in place of a shortened animation or just make it teleport.

2. Keyboard shortcuts.

3. Where's the monster? ;)

  import * as v from 'valibot';
  const OptionalKeySchema = v.object({ key: v.optional(v.string()) });
  type t1 = v.InferInput; // { key?: string }

  const UndefinedKeySchema = v.object({ key: v.undefinedable(v.string()) });
  type t2 = v.InferInput; // { key: undefined }

https://youtu.be/4ef0juAMqoE?si=fya1OCfUUR4n_gd1

I have some feedback on your homepage & messaging.

Initially scrolling the home page I thought it was a tool for viewing customer bug sessions, similar to TrackJS or Sentry.

Reading this post it became clear this is for product managers and/or team members to file bugs. The line "Built for everyone" on the home page threw me off.

I think if you make the distinction that this is an internal tool for teams vs. an external tool for tracking customer issues it might help make this messaging clearer.

I'm not sure of your plans (perhaps you also intend for external users to use it) this was just my first pass impression.

I think this is a great tool. The structured format combined with the information provided by the extension are what make it valuable to me. The last minute feature is also nice as re-creating bugs can be a PITA.

As a dev, I would ideally also want to be able to view stack traces with source maps, but having a consistent structured format combined with the extension data is enough of a value prop to start using it.

Now that I’ve thought about it what I’m actually trying to ask is…

What would it take to drop flight prices 50%?

Automated flights, a change in fuel technology, 0 marketing spend, reduced maintenance?

More specifically, what is the bare bones cost to transport a human from point a to b, safely, in the same or less time it takes a flight.

What is the long term plan here? Will there still be duo pilots in 2040? 2060?

Surely long term it will be automated with remote supervision/override and a cabin crew who have basic training to emergency land.

Do the testing on mail delivery, get it good enough, introduce it into domestic with pilots still present, slowly phase out pilots to be remote.

I would fly domestic automated flights if the automation was proven as safe, the above conditions were met, and the price was 40-50% cheaper.

I don’t see why a company hasn’t gone all in on this yet, but would love to hear why it’s a dumb idea/not feasible.

* Edit: based off this link it seems that staffing is only 12% of costs which would not address my criteria of significantly cheaper flights. https://aviation.stackexchange.com/questions/33770/how-much-...

Steps:

1. Settings > Screen time > Use screen time pass code > Enter a different passcode to your main one that you will remember

2. Settings > Screen time > Content & Privacy Restrictions > Scroll down to Account changes > Don’t allow

This prevents account changes from the device, unless you have the second passcode.

This would not prevent a thief who was aware of this (they could attempt to disable screen time then request the second passcode), but it would prevent a pickpocket who happens to see your passcode being entered from changing your iCloud account details.