Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with primevue package #7298

Open
1 of 4 tasks
TylerWanta opened this issue Feb 22, 2025 · 0 comments
Open
1 of 4 tasks

Issue with primevue package #7298

TylerWanta opened this issue Feb 22, 2025 · 0 comments
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@TylerWanta
Copy link

TylerWanta commented Feb 22, 2025

Describe the bug

I need to make some quick tweaks to the repo for my project. Because of this, I am trying to fork and publish the repo but am running into some issues. All I've done so far is change the name of the primevue package as well as create a github action to publish. Upon running the action, I get this error

Image

It looks like the build is failing while running pnpm run release on the monorepo. I'm guessing this means there are more nuances to the publishing process that I don't know about.

Here is my publish action:

name: Publish Package to npmjs
on:
  workflow_dispatch:
jobs:
  build:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      id-token: write
    steps:
      - uses: actions/checkout@v4

      - name: Install pnpm
        uses: pnpm/action-setup@v4
        with:
            version: 9.6.0

      - uses: actions/setup-node@v4
        with:
          node-version: '20.x'
          registry-url: 'https://registry.npmjs.org'
          cache: 'pnpm'

      - run: |
            pnpm run setup
            pnpm run release
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

Trying to publish it manually within VS Code gives a similar error.

Image

Would you please be able to explain how PrimeTek publishes the primevue package to npm, or provide a .yaml github action to accomplish it? I'd be more than happy to help document this process afterwards for future users.

Link to the forked repo: https://github.com/TylerWanta/primevue-tw

Pull Request Link

No response

Reason for not contributing a PR

  • Lack of time
  • Unsure how to implement the fix/feature
  • Difficulty understanding the codebase
  • Other

Other Reason

Not relevant

Reproducer

https://github.com/TylerWanta/primevue-tw

Environment

Forked Repo is all

Vue version

n.a

PrimeVue version

v4

Node version

No response

Browser(s)

No response

Steps to reproduce the behavior

Clone My repo and run the publish action

Expected behavior

Publish process is documented somewhere

@TylerWanta TylerWanta added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

1 participant