Hi there, I was just merging the upstream/develop in my feature branch and recreated the yarn.lock, realizing that I messed it up - when running yarn on the root directory, it cannot resolve the local packages, like > Couldn't find package "@packages/web-config@0.0.0-development" required by "@packages/desktop-gui@0.0.0-development" Any recommendations on how to fix this?

👋 what yarn version are you on and what node version @User

We work with node 12.18.3 and yarn 1.22.10

Recreating the yarn lock will cause a lot of problems

i suggest rm -rf node_modules and resetting the yarn lock and doing a

yarn

again at the root

it's aggressive, but we do a lot of crazy stuff like "patch-package" which writes to your node_modules

Tag me if you run into any issues

Well, while rebasing close to 40 commits I messed up one package json, that was the issue, just restored it from develop.

Hi folks, i am trying to run cypress on my vuejs project. any *spec.js open attempts give me this error message:

would anyone be able to help?

or point me to the right direction?

I'm not familiar with the problem but do you have any compilation config you could share?

Actually I would recommend creating an issue here: https://github.com/cypress-io/cypress/issues/new?assignees=&labels=&template=1-bug-report.md&title=

then link it here and I will help investigate

done - https://github.com/cypress-io/cypress/issues/15133

I don't see a description. Please use the issue template.

that's what i used, that's sucks.. not sure where it disappeared. let me try again.

pls check now.

Looks good now. We can continue from there. I left some comments already 😄

i saw it, will give it a try

FYI @User I responded here https://github.com/cypress-io/cypress/issues/15133

I'm sorry it took me so long!

@stocky-dream-36427 no worries, thank you!

Hi guys. So i'm using vuetify and i'm writing e2e tests. My problem is that i want to check if a v-select accepts multi-selection. Anyone know how can i pick values in a v-select?

Hey!

I think something like this would do

js
cy.get('#picker')
  .click()
  .children()
  .then(([first, second]){
    cy.wrap(first).click()
      .wrap(second).click()
      .get('body').click() // dismiss popper/overlay
}).should('contain', '' /* whatever is inside of the picker */)

it's been a while, but I can't for the life of me get Cypress to connect to localhost lol. Setting a baseUrl seems to "work", but it never connects (I can visit the baseUrl just fine in a new tab btw)

Oh sheesh... cy.get/find doesn't work, but cy.contains does.... Not sure why...

Some time ago I built a few vue components for a store-finder, including a map with store-icons, store-meta-information, a store-list component, a store search and some components handling URL query params to center the map to a certain store. The stores were loaded from an API providing location data (coordinates) and info. The map was a third-party component. back then I asked myself, I could test such a difficult setup. I wanted to see things like: - I click on a certain item within the list -> does the map center this very store? - if I enter a url with some query params including a store id -> will that store be expanded in the list AND centered on the map? - If I click on an item on the map -> will already expanded items within the list close and the clicked one expands? I realized that with unit testing I can't do it. Do you have any tipps on how to test such a thing? I started to implement some headless browser stuff, where I really just mock user interaction and try to see if certain classes/ids would appear on screen, but it felt super clumsy and did not really provide too much value.