Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.

Conversation

@micgro42
Copy link
Collaborator

This is needed for the help-link to the spelling variant input

Bug: T298146

@github-actions
Copy link

@lucaswerkmeister
Copy link
Member

LGTM; why does CI complain that package.json and package-lock.json aren’t in sync? o_O

@micgro42
Copy link
Collaborator Author

No idea, but we might as well have a PR to update the dependencies on the next branch. But maybe after #594 is merged?

@lucaswerkmeister
Copy link
Member

Hm, I didn’t merge #594 yet because of the Node 16 requirement :/

micgro42 added a commit that referenced this pull request Jun 16, 2022
This is originally done in order to work around a CI failure in #597 that showed up as follows:

```
npm ERR! code EUSAGE
npm ERR! 
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm ERR! 
npm ERR! Invalid: lock file's acorn@7.4.1 does not satisfy acorn@8.7.1
npm ERR! Missing: acorn@7.4.1 from lock file
npm ERR! Missing: acorn@7.4.1 from lock file
npm ERR! Missing: typescript@4.7.3 from lock file
npm ERR! Missing: acorn@7.4.1 from lock file
```

The original cause is still unclear, but it was possible to reproduce that error by forcing `lerna bootstrap` to always perform a CI installation, even locally.

Fixing that issue resulted somehow in test failures like:

```
FAIL tests/unit/components/Lookup.spec.ts
  ● Test suite failed to run
    No element indexed by 27
      at ArraySet_at [as at] (node_modules/@vue/vue3-jest/node_modules/source-map/lib/array-set.js:92:9)
          at Array.map (<anonymous>)
      at mapLines (node_modules/@vue/vue3-jest/lib/map-lines.js:12:18)
      at processScript (node_modules/@vue/vue3-jest/lib/process.js:47:16)
      at Object.module.exports [as process] (node_modules/@vue/vue3-jest/lib/process.js:162:24)
```

which were solved by another `npm update` in `vue-components/`.

Co-authored-by: Lucas Werkmeister <lucas.werkmeister@wikimedia.de>
@micgro42 micgro42 force-pushed the next-LinkComponent branch from e436a35 to 460a4b5 Compare June 16, 2022 16:32
micgro42 and others added 2 commits June 16, 2022 18:53
This fixes the issue that "Link" is apparently a reserved word in HTML.
Renaming the filename seems unnecessary though.
@micgro42 micgro42 changed the title Migrate Link component to the next branch, i.e., Vue 3 Migrate Link component to the next branch Jun 17, 2022
@micgro42 micgro42 merged commit fbd9fce into next Jun 17, 2022
@micgro42 micgro42 deleted the next-LinkComponent branch June 17, 2022 09:27
micgro42 added a commit that referenced this pull request Jun 17, 2022
This was forgotten in #597

We really should have some test for this :/.
micgro42 added a commit that referenced this pull request Jun 20, 2022
This was forgotten in #597
We really should have some test for this :/.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants