https://cypress.io logo
Join DiscordCommunities
Powered by
# general-chat
  • n
    seems ok now, had no issues all morning
  • n
    thanks for sorting it out. btw i checked statuspage, but there was no information on this. I didn’t know whether I should report it or not and if you are aware 🙂
  • s
    Thanks for the ping, it’s definitely welcome 🙏🏻
  • g
    oh good
  • g
    this will be helpful. 😄
  • a
    hmm I did 
    yarn add @cypress/webpack-preprocessor
    . it specifes 
    dist
    as the 
    main
    in 
    package.json
    but nothing inside there when I look in node_modules. Looks lke something got busted during the monorepo migration
  • a
  • s
    Hey. Thanks.
  • s
    I thought this was a build only issue last night. We changed circle CI and likely broke it. Fixing it now
  • g
    HN is discussing testing crab https://news.ycombinator.com/item?id=24980263
  • s
    Nice!
  • u
    I just started learning Vue.js , completely beginner. I am looking for few people who are new to Vue too. Learning together is fun, in a small group like 5-10 people. In a group of hundreds or thousands, many people usually ignore the questions and doubts, that's why I decided to make a telegram group. Let me know if u want to join. if you are beginner and ready to learn together and help each other.
  • s
    If I want to assert that my app made a request without letting the request hit a real server, would I use 
    route2
    ?
  • n
    you can use route() too, just make sure you stub it
  • s
    Thanks, @User. I was under the impression that stubbing a response just overwrites the response coming back.
  • s
    the *real response
  • s
    No, it can prevent it. It's an optional pass-through
  • s
    You should use route2 if possible -- we tried to cleanup the API and it also has better support because it's a proxy-level interception instead of a client-side one
  • s
    @User ^ 🙇‍♀️
  • s
    Thanks, @User is 
    route2
    a drop-in replacement if I'm using the 
    cy.route(method, url)
    implementation?
  • s
    I wish 🙂
  • s
  • s
    It will soon move to be the main way, so you should use it
  • n
    how soon? I’m wondering about the migration process. that might be a loooong transition
  • s
    I don't think the migration will be that heavy -- it depends on what features you use
  • s
    Give it a try @User, you can use both at the same time.
  • n
    I actually using it a lot, even wrote a blog about it already 😄 I mostly use route() command for waiting for api responses and then checking the response body. At the moment I often use combination of both, they seem to play well together, but it seems they are using slightly different options and I feel that there may be some migration to be done once the route() command becomes deprecated
  • s
    ah... ok
  • b
    @User here are some more details on the plans for eventually replacing cy.route with cy.http: https://github.com/cypress-io/cypress/pull/4176#issuecomment-731272367 we don't plan on breaking cy.route for a while, and it will be available as a plugin even when it's no longer in core, since as you say many people have elaborate setups using cy.route
  • n
    Thanks Zach, I’m subscribed to the issue I was glad to read your comment today 👍 I think it is a very good direction. Immediately I thought that aliases made with this command should have different color - spies are red, DOM elements are blue, network requests are yellow, maybe http() could be purple 🙂 if people are going to be using both route and http, I think the color distinction might be useful
12345...127Latest