chore(deps): repin @conduction/nextcloud-vue to 2.2.0-vue3.3 (3.0.0-vue3.6 was unpublished) - #278
Merged
Merged
Conversation
…ue3.6 was unpublished)
Contributor
Quality Report — ConductionNL/scholiq @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| check-specs | ✅ | ||||
| composer | ✅ | ✅ 100/100 | |||
| npm | ✅ | ✅ 750/750 | |||
| PHPUnit | ✅ | ||||
| Newman | ⏭️ | ||||
| Playwright | ⏭️ | ||||
| Hydra gates | ❌ |
Quality workflow — 2026-08-05 15:12 UTC
Download the full PDF report from the workflow artifacts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
@conduction/nextcloud-vue3.0.0-vue3.1…3.0.0-vue3.6were unpublished from npm, and npm never permits reuse of an unpublished version number — the old pin is permanently dead:npm citherefore cannot succeed ondevelopment. Fleet-blocking.What
3.0.0-vue3.6— dead (E404)2.2.0-vue3.3— live, currentvue3dist-tagpackage-lock.jsonPinned exactly (no caret), per fleet convention.
Verification
npm cifailMissing: … from lock filewhile a localnpm cistill passes. Using npm 10 avoids that false green.npm ci(fresh isolated cache, npm 10.8.2): exit 0, zeroMissing:lines.USE_LOCAL_LIB=false npm run build: exit 0, 0Module not found, 0export … was not found. (USE_LOCAL_LIB=falsematters —webpack.config.jsaliases the package to a sibling../nextcloud-vue/srccheckout when present, so a plain build can compile the sibling and prove nothing about the pin.)npm run test:js-unit(node --test): 5/5 passing. This repo has no vitest/jesttestscript.A "before" run is impossible —
npm cicannot install the dead pin, so no baseline number exists.src/imports from@conduction/nextcloud-vueresolve against the installed 2.2.0-vue3.3 (574 exports).One thing worth recording
src/components/admin/ActionAuthMatrix.vueimportsNcButtonandNcCheckboxRadioSwitchfrom@conduction/nextcloud-vuerather than from@nextcloud/vue. That is fine: nc-vue's ESM entry doesexport * from '@nextcloud/vue', so both names are genuinely re-exported (confirmed in@nextcloud/vue@9.9.0'sdist/index.mjs), and the build emits noexport … was not found. Noting it because the indirection is load-bearing — if nc-vue ever drops that blanket re-export, this file breaks silently with no build error.Scope
Only
package.json+package-lock.json. The bundle is gitignored here (no trackedjs//dist/). E2E (playwright) not run — needs a live Nextcloud instance.