-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Use Electron ASAR to optimize file system access? #36997
Comments
@auchenberg we already benefit from the fact that most of our JS code is bundled into a single file. I think where a concept like ASAR could only help us is with node modules access which in our case is not bundled in any way. /cc @alexandrudima who recently looked into ASAR when checking for file access on startup. |
👍 |
What's the planned action here for November 2017? I'm seeing this everytime I update VSCode Insiders, that they are literally hundreds of thousands js files. |
Investigation results - #41353 |
Pushed via #41353 |
We have discovered at least 17 extensions that might make assumptions about the the core We need to communicate with these authors and understand their needs, plus give sufficient time to prepare for the change. |
After downloading all our extensions, and running searches over them, there are only 8 affected extensions: ☑
|
One more to add to your list. This extension is used as a dependency by other extensions as wells: https://github.com/siegebell/scope-info/blob/master/src/text-mate.ts#L2 Thanks |
Have we considered using Electron's ASAR to optimize file system access? I imagine this could especially help Windows launch performance.
Found this old write-up from N1/Atom: atom/atom#10163, but it seems that they have moved away from it. Is ASAR considered obsoletely? @Tyriar
The text was updated successfully, but these errors were encountered: