Test-proxy issue in build version 2.2.2-rc.2

[lynchem]

Sorry it took me a while to actually deploy this to staging and test it but in doing so I realised something was introduced between 2.2.2-rc.1 and 2 that caused our build pipeline to fail. I'll look back at the PRs merged now and see if I can spot it.

I tried to reproduce locally by running in production mode but must be triggered only during a build.

2025/08/26 13:19:14.772843 [ERROR] An error occurred during execution of command [app-deploy] - [StageApplication]. Stop running the command. Error: chown /var/app/staging/programs/server/npm/node_modules/meteor/aldeed_tabular/test-proxy/node_modules/@babel/runtime/helpers: no such file or directory 

update 1

Can't see any trouble building locally or looking through the diff of changes.

update 2

@jankapunkt - could this text-proxy stuff have gotten into the 2.x release somehow ? I don't see it mentioned so it's weird.

[github-actions[bot]]

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously. Our goal is to provide long-term lifecycles for packages and keep up with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time. Therefore, we can't guarantee your issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit a pull request, too! We will accompany you in the process with reviews and hints on how to get development set up.

Please also consider sponsoring the maintainers of the package. If you don't know who is currently maintaining this package, just leave a comment and we'll let you know

[jankapunkt]

Hey @lynchem the test-proxy is only used for tests and should not be part of the package at all. How is your CI running actually? Do you clone this repo for building or simply include the package in .meteor/packages?

[lynchem]

Hey Jan, nothing special, just an npm ci - no idea how it's triggering this. It seems test-proxy includes puppeteer which has a postinstall script which is being triggered. But test-proxy is a dev dependency 🤷🏻 I tried building locally and got this.

> [email protected] postinstall /home/mark/code/t/bundle/programs/server/npm/node_modules/meteor/aldeed_tabular/test-proxy/node_modules/puppeteer
> node install.mjs
Skipping browser installation because the Puppeteer build is not available. Run `npm install` again after you have re-built Puppeteer.
@babel/[email protected] /home/mark/code/t/bundle/programs/server/npm/node_modules/meteor/aldeed_tabular/test-proxy/node_modules/@babel/code-frame
@babel/[email protected] /home/mark/code/t/bundle/programs/server/npm/node_modules/meteor/aldeed_tabular/test-proxy/node_modules/@babel/helper-validator-identifier
[email protected] /home/mark/code/t/bundle/programs/server/npm/node_modules/meteor/aldeed_tabular/test-proxy/node_modules/js-tokens
[email protected] /home/mark/code/t/bundle/programs/server/npm/node_modules/meteor/aldeed_tabular/test-proxy/node_modules/picocolors

Don't worry about it though unless there's issues in the 3.x branch. We copied the package locally now and all's good. Eventually we'll get our act together and get onto Meteor 3 too 😅