Meteor-Community-Packages / Meteor-Community-Packages/meteor-tabular
Test-proxy issue in build version 2.2.2-rc.2
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 360
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the changes between builds 2.2.2-rc.1 and 2.2.2-rc.2, focusing on the deployment build rather than production-mode local runs. Investigate why test-proxy/node_modules/@babel/runtime/helpers is referenced during app-deploy, then verify that the staging build completes without the missing-path error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100