NPM package not publishing

[markacato]

@matijs @Robbert is er een manier om een NPM package te publiceren met de Tilburg componenten? Momenteel lijkt dat nog niet goed te gaan in de build: https://github.com/nl-design-system/tilburg/actions/runs/13132228766/job/36639725611

Run pnpm config set "//registry.npmjs.org/:_authToken" "${NPM_TOKEN}"

> @tilburg/[email protected] publish /home/runner/work/tilburg/tilburg
> lerna publish from-package --yes

lerna-lite notice cli v3.10.0
lerna-lite info versioning independent
lerna-lite info ci enabled
lerna-lite WARN Unable to determine published version, assuming "@tilburg/design-tokens" unpublished.

Found 1 package to publish: 
 - @tilburg/design-tokens => 1.0.0-alpha.44

lerna-lite info auto-confirmed 
lerna-lite info publish Publishing packages to npm... 
lerna-lite WARN lifecycle Skipping root "prepublish" because it has already been called
lerna-lite info lifecycle @tilburg/[email protected]~prepare: @tilburg/[email protected]

> @tilburg/[email protected] prepare /home/runner/work/tilburg/tilburg
> husky

lerna-lite WARN notice Package failed to publish: @tilburg/design-tokens
lerna-lite ERR! E404 Not found
lerna-lite ERR! errno "undefined" is not a valid exit code - exiting with code 1
lerna-lite ERR! E404 Not found
node:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

HttpErrorGeneral: 404 Not Found - PUT https://registry.npmjs.org/@tilburg%2fdesign-tokens - Not found
    at /home/runner/work/tilburg/tilburg/node_modules/.pnpm/[email protected]/node_modules/npm-registry-fetch/lib/check-response.js:95:15
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async publish (/home/runner/work/tilburg/tilburg/node_modules/.pnpm/[email protected]/node_modules/libnpmpublish/lib/publish.js:53:15)
    at async file:///home/runner/work/tilburg/tilburg/node_modules/.pnpm/[email protected]/node_modules/p-pipe/index.js:10:19
    at async file:///home/runner/work/tilburg/tilburg/node_modules/.pnpm/[email protected]/node_modules/p-queue/dist/index.js:187:36 {
  name: 'ValidationError',
  headers: [Object: null prototype] {
    date: [ 'Tue, 04 Feb 2025 09:26:05 GMT' ],
    'content-type': [ 'application/json' ],
    'content-length': [ '21' ],
    connection: [ 'keep-alive' ],
    'cf-ray': [ '90c99df899caad43-ORD' ],
    vary: [ 'Accept-Encoding' ],
    'set-cookie': [
      '_cfuvid=05BQ6.UbOZHbTYeIR0uXq2Zch.TfQvAQ2Rlnp_KLzKA-1738661165476-0.0.1.1-604800000; path=/; domain=.npmjs.org; HttpOnly; Secure; SameSite=None'
    ],
    server: [ 'cloudflare' ],
    'x-fetch-attempts': [ '1' ]
  },
  statusCode: 404,
  code: 'E404',
  method: 'PUT',
  uri: 'https://registry.npmjs.org/@tilburg%2fdesign-tokens',
  body: { error: 'Not found' },
  pkgid: '@tilburg/[email protected]'
}

Node.js v20.11.1
 ELIFECYCLE  Command failed with exit code 1.
Error: Process completed with exit code 1.

[markacato]

Waarschijnlijk ook related aan #82 denk ik @hansregeer?

[matijs]

Dat zouden we wel kunnen regelen maar de @tilburg scope is er nog niet, of is private zo te zien. Weet jij wie daar over gaat?

[markacato]

@matijs ik weet niet wie daarover gaat nee. Wat is gebruikelijk? Is dit iets dat wij als leverancier van de website regelen, komt dit vanuit het NLDS of moet dit bij Tilburg intern worden opgezet?

[matijs]

Vanuit NL Design System kunnen we @gemeente-tilburg gebruiken. Ik heb een issue aangemaakt

[markacato]

Super, thanks @matijs!