[mshima]

Summary

Importing the Store from the package loads the whole index: the environment, mem-fs-editor, the adapter and inquirer, the conflicter, commander… A tool that only looks up and reads generators (lookupSync, getMeta, requireSibling) does not need them.

• yeoman-environment/store: a subpath exporting the Store (as Store and as default) and the types of the store (StoreGeneratorMeta, StoreLookupOptions, …), without the environment.
• execa out of the store: the store imported execa through the lookup of the global npm paths (yarn global dir, npm root -g). execaOutput now loads it at its first command: a lookup given the paths of its packages does not load it. execa is kept rather than child_process, for the .cmd of npm and yarn on Windows.

Benchmark

Modules loaded by an import:

	before	after
dist/store.js	179	31
yeoman-environment/store	–	32
yeoman-environment	400	400 (the environment uses execa to install)

Test plan

• npm test (eslint, prettier, tsc, the tests)
• The exports of the store entry; a lookupSync with packagePaths and a requireSibling through yeoman-environment/store, without loading execa

🤖 Generated with Claude Code