stackblitz-labs / stackblitz-labs/pkg.pr.new
prepublish behavior not triggered anymore?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
I've used pkg.pr.new a while and recently the prepublishOnly script doesn't seem to be triggered anymore, which means the build folder is not generated in our PR previews.
We've now included it in the Github Workflow manually - but I think it makes sense that the behavior replicates npm publish as close as possible, right?
Contributor guide
No contributing guide indexed for this repository
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 examining the GitHub Workflow and the pkg.pr.new publishing path to determine whether npm's prepublishOnly lifecycle is invoked. Reproduce a PR preview and verify that the build folder is generated without the workflow's manual build step; no specific source file or test is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100