Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Josh Justice
    @CodingItWrong
    👍
    Thanks for checking out the guide! I'll do my best to get you up and running
    One more option is Reactiflux, the React Discord server. Someone there might also have ideas
    Josh Justice
    @CodingItWrong
    @alireza-chassebi I pulled down your repo and was able to see the error as well. Two options for you:
    1. I just created a repo that does work for me locally that you're welcome to use as the basis for yours: https://github.com/CodingItWrong/opinion-ate-temp - Something about the steps I followed was different. It looks like you're using npm, whereas I'm using yarn, and CRA hooks in to one or the other initially. But I switched over to npm and the package-lock.json file, and it still succeeds for me.
    2. The error seems to be coming from Cypress, so you could open an issue for them on their GitHub repo, and give them a link to your project repo: https://github.com/cypress-io/cypress/issues
    alireza-chassebi
    @alireza-chassebi
    thanks ill try it i was initially using yarn and it didnt work so i tried it with npm and it still did not work
    :) thanks for the help
    NRVIII
    @NRVIII
    hi! really enjoying the approach of TDD. Stopped at api => page is returning a HTTP 502
    any help?
    NRVIII
    @NRVIII
    just created a server in express to learn :thumbsup:
    Josh Justice
    @CodingItWrong
    @NRVIII Sorry for that error; the address of the API has changed and I forgot to update it on the site. It's been corrected now. The address is https://outside-in-dev-api.herokuapp.com/ - I've confirmed that it's working for me there now
    NRVIII
    @NRVIII
    thx for your help! Just a feedback, but the heroku is not working for me . Maybe because I am from Brazil? When enter put the site starts an infinite loading and presents the message "This page is not working"...
    Josh Justice
    @CodingItWrong
    Sorry, I'm not sure. This site reports that the API is up, so it might just be you: https://downforeveryoneorjustme.com/outside-in-dev-api.herokuapp.com
    NRVIII
    @NRVIII
    image.png
    for me is down, maybe is locked by region
    Josh Justice
    @CodingItWrong
    @NRVIII Ok, I tried adjusting a setting on the servers, so its possible it will work now. That monitoring site is showing success for me again
    NRVIII
    @NRVIII
    image.png
    working!!! Thanks for your help!! And indeed, for this incredible course!
    Josh Justice
    @CodingItWrong
    You're very welcome. Thanks for letting me know so I could fix up the server for others too
    NRVIII
    @NRVIII

    You're very welcome. Thanks for letting me know so I could fix up the server for others too

    :thumbsup: :thumbsup:

    Bernard Amofah
    @bamofah

    hi first of thanks for the great tutorial. I am having some issues from the gat ego. when i try and run yarn cypress i get the following
    Cypress could not verify that this server is running:

    http://localhost:3000

    This server has been configured as your baseUrl, and tests will likely fail if it is not running.

    I get this when running on wsl but on windows I get the following errors

    Cypress failed to start.

    This is usually caused by a missing library or dependency.

    The error below should indicate which dependency is missing.

    https://on.cypress.io/required-dependencies

    If you are using Docker, we provide containers with all required dependencies installed.

    Would greatly appreciate your assistance

    image.png
    Josh Justice
    @CodingItWrong
    @bamofah Sorry you're running into errors! For the error about http://localhost:3000 not running: if you visit http://localhost:3000 in a browser, does it work? If not, make sure to run your application using yarn start for the React exercises or yarn serve for the Vue exercises.
    If that doesn't help, I'd recommend asking on the Cypress Gitter: https://gitter.im/cypress-io/cypress
    Bernard Amofah
    @bamofah
    i think i found the issue. the instructions didn't state that one needs to have the app running first before running cypress
    Josh Justice
    @CodingItWrong
    @bamofah Ah, sorry about that. I've written down a todo to go through the book and add explicit reminders to make sure the app is running.
    So hopefully that'll help prevent that for folks in the future.
    Abraham Brookes
    @AbrahamBrookes
    hey I'm running through the edge cases vue exercise here and getting a weird error coming from the vuetify v-alert component.
    As soon as I add the type property to the v-alert component I get a slew of red compilation errors in my console and a bunch of my tests start failing - the most prominent error being TypeError: Cannot read property 'component' of undefined
    which looks like it is originating from the call to the vue-test-utils@mount function
    image.png
    I'm thinking this is a vuetify error in particular:
    Abraham Brookes
    @AbrahamBrookes
    I have just pushed a PR to my repo if anyone wants to have a look: AbrahamBrookes/outsidein-dev-opinion-ate#4
    the app is compiling ok and showing the v-alert component:
    image.png
    I think the v-alert component doesn't like the tests local vue instance or smth?
    Abraham Brookes
    @AbrahamBrookes
    if I simply remove that prop the tests run as expected, but my component is obviously not working properly
    image.png
    image.png
    wrapper is undefined because the v-alert error is causing the call to mount to fail, resulting in my let wrapper variable to never be assigned to
    excellent guide btw, the page on setting up the environment with CI and netlify alone is easily the best setup guide for the full pipeline I have ever seen - have shared it with my colleagues and they are all quite impressed
    Abraham Brookes
    @AbrahamBrookes
    I was on vuetify 2.4.0, just upgraded to 2.4.5, same error
    Abraham Brookes
    @AbrahamBrookes
    I'm dropping the v-alert component in favour of a div for now since I'm pretty sure that error is out of scope and I don't want to get distracted!
    Abraham Brookes
    @AbrahamBrookes
    image.png
    Abraham Brookes
    @AbrahamBrookes
    hey with this section: https://outsidein.dev/vue/6-writing-data.html#validation-error it seems like you're going back on what you've said earlier wrt leaving the text content itself up to the implementation
    image.png
    seems like that should be a toExist() instead?
    also what's with that trailing comma? seems like that should throw a syntax error
    and that v-alert component is still chucking wobblies - here's the full error stack I've just got
    Abraham Brookes
    @AbrahamBrookes
     FAIL  tests/unit/components/CreateRestaurant.spec.js
      ● Console
    
        console.error node_modules/vue/dist/vue.runtime.common.dev.js:621
          [Vue warn]: Error in render: "TypeError: Cannot read property 'component' of undefined"
    
          found in
    
          ---> <VIcon>
                 <VAlert>
                   <Anonymous>
                     <Root>
        console.error node_modules/vue/dist/vue.runtime.common.dev.js:1884
          TypeError: Cannot read property 'component' of undefined
              at remapInternalIcon (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vuetify\dist\webpack:\Vuetify\src\util\helpers.ts:225:39)
              at VueComponent.getIcon (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vuetify\dist\webpack:\Vuetify\src\components\VIcon\VIcon.ts:72:31)
              at Proxy.render (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vuetify\dist\webpack:\Vuetify\src\components\VIcon\VIcon.ts:217:23)
              at VueComponent.Vue._render (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:3538:22)
              at VueComponent.updateComponent (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:4054:21)
              at Watcher.get (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:4465:25)
              at new Watcher (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:4454:12)
              at mountComponent (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:4061:3)
              at VueComponent.Object.<anonymous>.Vue.$mount (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:8392:10)
              at init (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:3112:13)
              at createComponent (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:5958:9)
              at createElm (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:5905:9)
              at createChildren (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:6033:9)
              at createElm (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:5934:9)
              at createChildren (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:6033:9)
              at createElm (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:5934:9)
              at VueComponent.patch [as __patch__] (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:6455:7)
              at VueComponent.Vue._update (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:3933:19)
              at VueComponent.updateComponent (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:4054:10)
              at Watcher.get (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:4465:25)
              at new Watcher (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:4454:12)
              at mountComponent (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:4061:3)
              at VueComponent.Object.<anonymous>.Vue.$mount (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:8392:10)
              at init (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:3112:13)
              at createComponent (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node_modules\vue\dist\vue.runtime.common.dev.js:5958:9)
              at createElm (C:\Users\kjabd\Projects\outsidein.dev\opinion-ate\node
    oh I've been truncated