Request for Documentation (specifically what remix-pwa does for you on install) #46
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
high priority
An issue that is one of my top priority with regards to remix-pwa
new feature
I've got a great idea for remix-pwa
Background:
I'm really excited about this project cause I already love Remix and want to have an easy way to create a close to native experience. I was able to get a fresh remix-blues stack up and running with remix-pwa, although I had to remove cypress testing from my CI/CD since Electron was giving me issues and it was just beyond my understanding at this time.
Issue:
I read as much as I could from the README and the Roadmap but I still have questions on how I could learn some of the under the hood implementations or what APIs are directly touched by remix-pwa. I'd love to be able to help on the project or give better feedback but it's hard to know what remix-pwa does or doesn't do. I mean that in the sense of, I see some code generation happening when using the CLI tool, but I had issues using that same CLI tool on a remix application I already have in production, as a result some features of the library are definitely not working after I tried filling in what I could see from a successful fresh install.
Request:
Final Note:
This is a really amazing project and makes Native Application support seem like an achievable goal for anyone with a remix stack already, I'd just love to have extra documentation so I can do something to help the project along and have more confidence in using it on existing applications.
Edit:
Dug through other issues and found the reason i had CLI issues on an existing project. Comments do seem to break the CLI, removing them all has fixed the issue. Added request 4. as a reuslt.
The text was updated successfully, but these errors were encountered: