perf(vite): simplify manifest property acccess

[GalacticHypernova]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR caches each key in the client manifest to improve performance and decrease the manifest handling time. Tested with core-js package.json file, performance is increased by ~90% (view second attachment):

And with native console.time/timeEnd:

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[GalacticHypernova]

(The failing test has nothing to do with the PR whatsoever, and might be worth fixing in the test case itself)

[danielroe]

This is run once after the vite build, and iterates over every file emitted from the vite client build.

I would not imagine there is a significant difference in time between 6x accesses of a deep property and 1x access of deep property and 5x one level less. But I'm happy to be proved wrong.

How did you run the test in the issue?

[GalacticHypernova]

@danielroe
clientManifest is the core-js package-lock.json file (won't paste it here because it's too large), BASE_RE is new RegExp('abcde')
Rest of the code is:
repeatedIndex: the same as the current file
cachedAccess: this PR
Same goes for all my perf PR's

Offline testing supports this as well: