Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a better way to deal with lack of resource manifest in DEV #2

Open
DanielBaulig opened this issue Nov 11, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@DanielBaulig
Copy link
Owner

Currently we simply don't load the resource manifest and don't try to cache the app resources. This makes development easier and simpler, but also means that the code path is only tested if explicitly built and run in preview mode.

npm run build && npm run preview

And any issues that need to be debugged within that setup have to be debugged in minified code, which makes it a real headache. I need to find a way how I can reasonably run the resource manifest / app resource cache code during development, too. Maybe point the resource manifest at a dummy manifest that contains some dummy app resources.

@DanielBaulig DanielBaulig added the enhancement New feature or request label Nov 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant