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

Comments

Next: Update some dependencies#598

Merged
micgro42 merged 8 commits intonextfrom
next-updateEslint
Jun 16, 2022
Merged

Next: Update some dependencies#598
micgro42 merged 8 commits intonextfrom
next-updateEslint

Conversation

@micgro42
Copy link
Collaborator

The TextInput component was adjusted to satisfy the error message:

94:3  error  Name "Input" is reserved in HTML  vue/no-reserved-component-names

@github-actions
Copy link

@micgro42
Copy link
Collaborator Author

I don't get it. The error is here as well!?

Also, about that npm warning - where the heck is the eslint-plugin-vue@6.2.2 coming from in the first place?

@lucaswerkmeister
Copy link
Member

The TextInput component was adjusted to satisfy the error message:

Doesn’t that also need to be changed in LookupInput.vue?

@micgro42
Copy link
Collaborator Author

The TextInput component was adjusted to satisfy the error message:

Doesn’t that also need to be changed in LookupInput.vue?

Mh, good point. But it didn't complain for LookupInput.vue 🤔. The only difference that I notice as first glance would be how the Input component is imported in each case?

@lucaswerkmeister
Copy link
Member

This is very strange, everything seems to be green locally (so, the package/lock errors aren’t there, but also, eslint isn’t complaining about LookupInput). I’m confused…

micgro42 added 6 commits June 16, 2022 10:36
Maybe this will help in figuring out problems that show up only in CI
and not locally.
Since version 0.18.0 the wikimedia/node package includes linting for
.json files. So we use that instead of using our own. Also, this now
fixes some inconsistent spacing in some json files.

Further, this installs eslint-plugin-jsdoc as a dependency, because
otherwise eslint complains, even though we do not use it directly.
The wikimedia/client config pulls in client-es5, so if we actually want
es6 linting, then we should use wikimedia/client-es6.
That also complains about some shadowed variables, which are fixed in
this commit as well.

This adds eslint-plugin-es as a dev dependency, because somehow eslint
does not manage to find it as a dependency of eslint-config-wikimedia.
It is unclear how or why the package-lock files became out of sync, but
adding --ci to the lerna bootstrap command allowed to reproduce and
subsequently fix the issue.
This fixed all component test suites failing with an error similar to:

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)
@micgro42
Copy link
Collaborator Author

(This still works for me locally with node 14)

Copy link
Member

@lucaswerkmeister lucaswerkmeister left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM apart from some leftover debug output (I assume); also works for me in Fresh

Co-authored-by: Lucas Werkmeister <lucas.werkmeister@wikimedia.de>
@micgro42 micgro42 changed the title Update eslint-related dependencies Next: Update some dependencies Jun 16, 2022
@micgro42 micgro42 merged commit 7e68001 into next Jun 16, 2022
@micgro42 micgro42 deleted the next-updateEslint branch June 16, 2022 16:32
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.

2 participants