-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Update cleanup directory defaults #467
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep this seems fine. I'm ignoring the failing test as it won't apply in the context where this new config gets used, but I can't merge and release this until that Minify command is gone
I see. I can delete the minify command aswel. The Edit: This does raise the question of where things belong. The minification / cleaning step is now part of the copy step of the build command on the electron repo. I could argue that that piece of functionality should actually live in this repository. What do you think? |
Yeh I've found this to be a bit of a challenge. I think this stems from the fact that only have this Laravel adapter and the Electron driver. It may become clearer if/when we add more drivers and adapters... I have thoughts on how we may divide this better, but I'm keen not to over-engineer stuff on this front until it becomes more obvious. Maybe for now we do what works and refactor once it becomes clear? |
On not merging... actually, maybe we can... I don't think that minify command is even being used any more, right? |
Minify command is not used anymore. You even deleted it from your original obfuscation PR: 8b929a6 |
I just noticed something. Slight oversight on my part. Since the app cleaning is done before running Without the dev dependencies, the footprint still is very small (20kb) in a fresh app. |
Let's do the extra pass AND remove it from the config array |
Cool! I've added that here NativePHP/electron@550922d I've also removed
I moved the list of default patterns to the internal config, this way the definitions are at least inside the laravel repo. Is that okay? I can move them back. Edit: moved them back. The tests live in the electron repo right now so it's easier if it's not spread out. Still makes sense to move everything that only touches the Laravel side of things over to this repo in my mind. The boundaries of each repo's responsibilities become a bit vague. I left the |
This is hard to test when the config I'm asserting on lives on a different repo from the test itself.
Accompanies PR NativePHP/electron#153
storage/app/framework/{sessions,testing,cache}
&storage/logs/laravel.log
have been moved to the build command default exclude patterns. Since They should aways be excluded from the final build because of security concerns.I've added
vendor/bin
&node_modules
as sensible defaults to be tweaked.@simonhamp What do you think about this? If accepted this should be mentioned in a update guide.