Removing a runtime from a template ZIP gives the recipient setup work beyond extraction. A smaller file needs instructions about the required tools, the working directory and the commands to run.
The first request was for a package that could run on another PC with Windows and Mac runtimes included. A later correction left those runtimes out because the tools were already installed, with the prerequisites moved into the README. That changed the recipient’s work as well as the archive size. The guide, packaging code and verification records show how.
Begin with what the receiving computer already has
The earlier combined package included Node.js runtimes for Windows and the relevant Mac CPU architectures, dependencies, launchers and a preview. It was intended to start without a separate Node.js installation. After the owner chose to use installed tools, the template-only package excluded runtime executables, installers, node_modules, example builds and review captures.
The current README requires Node.js 22 or later and npm. To install the project dependencies, the recipient needs internet access or the required packages in the npm cache. Node.js alone does not provide those project packages. A package that leaves out the runtime still needs to explain this setup step.
The choice depends on the recipient. A template-only ZIP may be unsuitable for a computer where installing tools is difficult. Someone who already has those tools has less reason to receive executables for several operating systems. That decision belongs before adjusting compression settings.
Separate what to reinstall from what to copy
The inspected source-only builder leaves out runtimes and installed dependencies while retaining screen code, fonts, shared icons, input forms, the design contract and licences. It keeps the material needed to adapt the template and excludes generated preview output.
After a new site is generated, its hidden .engine directory matters. The README says to include it when moving that site again, and the site’s build command refers to code inside it. Copying visible site material while missing a hidden directory can leave a command that worked on the original computer unable to run on the next one.
Reinstalling dependencies is a documented setup step. Leaving out the template engine is a missing-file problem. The README should list what to install separately from what must be copied with the project.
Include the working directory with installation commands
The actual README installs dependencies in the template-engine folder, generates a new site, then installs dependencies in that site’s folder too. npm ci appears twice because its working directory changes. Commands without those directory changes could look like a request to repeat installation in the same project.
The example below changes only the new site name in the guide to example-site. I did not run it for this article. The generated site still needs its actual images, copy and source material. According to the README, the empty forms lack required material and therefore cannot pass the build checks.
After filling in the material, run npm run preview:build and npm run preview from the new site folder. This preview blocks actual registration and email delivery. Being able to inspect a page does not establish an operational enquiry connection.
Explore the implementation
Installation sequence from the template guide; folder name is illustrative
cd "현장교체형"
npm ci
node scripts/cli.mjs init --output "../example-site"
cd "../example-site"
npm ciMatch verification evidence to the delivered version
Historical records for the source-only package describe extraction into a separate path, preparation using README commands, creation and building of a new site, and checks of local route responses. They also record that an original-source preservation comparison was skipped because the original operational material was excluded. Passed and skipped checks should remain distinct.
The delivery ZIP was refreshed after a star effect changed. For the original article, I compared the retained ZIP’s bytes and hash with the latest package receipt, rather than using the first archive’s digest. Its README also matched the source guide at that time. This checked the connection between the file and the record; installation and product tests were not repeated.
Historical Windows execution and Mac file, execution-permission and script checks cover different scopes. The original guide leaves execution on physical Mac hardware unverified. Using the same Node.js commands on both systems should not be described as completed execution on every computer.
Alongside file size, the recipient needs the remaining setup requirements. A README can state whether tools are bundled, how to install dependencies, where the generated site’s engine and material belong, and which stages were checked in which environment. I compared those conditions for this article without rebuilding, installing, deleting or deploying the original package.