Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yes. You can see this among other planned use cases for the web packaging spec here https://wicg.github.io/webpackage/draft-yasskin-webpackage-u...


I'm not quite following which parts were or weren't needed for what's been enabled in the post here, for the usecase of delivering a single offline package that can be opened like a website, is there something that works yet? Or a repo I should be following other than the spec?

Once I can create webpackages and deliver them to clients a lot of thing I want to do become hugely easier and nicer.


I believe Chrome has already shipped an implementation, I don't know any more details unfortunately. It's still in the standardization process.

I know it's not exactly easy to follow but the only implementation repo I can think of to follow right now is the Chromium repo.


Oh interesting! I'll see what I can find there, thanks!

I also had a look in the blog and the "progressive web apps" might be the right thing to look at. There's probably something subtle that's different but I think I can use these to solve the actual problem I have.

https://developers.google.com/web/updates/2019/03/nic73?hl=h...

edit - damn, I don't think this is right at all. Frustrating as it seems pretty perfect but I have to serve from my own domain for 30s before a user can install it :( I just want a single file way of delivering web content! It seems like all the features are basically there, just with restrictions to focus on different use cases.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: