https://cypress.io logo
Join Discord
Powered by
# vue
  • s
    @User thanks for taking a look. I tried #1 by removing node-sass and adding sass, #2 i think with my updates in support/index.js and #3 by adding support/index.js but the change didn't enable my test to use my styles.
  • s
    @User thank you, i'll push what i have so you can see what i did
  • b
  • b
    @User especially look at the comments
  • b
    I hope it helped a bit
  • s
    @User thank you, i merged and trying to get working on my machine now. i deleted node_modules and waiting on it to finish reinstalling....it wouldn't start the first time i tried to npm install and npm run cy:open
  • s
    Here is what i have ERROR in ./assets/css/main.scss (./node_modules/css-loader/dist/cjs.js??ref--7-oneOf-1-1!./node_modules/postcss-loader/src??ref--7-oneOf-1-2!./node_modules/sass-loader/dist/cjs.js??ref--7-oneOf-1-3!./node_modules/sass-resources-loader/lib/loader.js??ref--7-oneOf-1-4!./assets/css/main.scss) Module build failed (from ./node_modules/sass-loader/dist/cjs.js): TypeError: this.getOptions is not a function This is running the updated branch
  • b
    this looks like sass-loader acting up what version of node are you using ?
  • s
    v14.16.1
  • b
    installing now fnm FTW
  • b
    So actually the problem is the version of sass loader we installed is on ly compatible with webpack 5...
  • b
    need to bring back v10
  • b
    Copy code
    json
{
  {
    "sass-loader": "^10.1.1",
    "vue-jest": "^3.0.4",
    "webpack": "^4.0.0",
    "webpack-dev-server": "^3.11.2"
  }
}
  • b
    this is the last 4 lines of the package.json and it works
  • b
    notice that I manually added webpack even if it might not be necessary
  • s
    Thank you!! it works with and without the webpack line but I will add it anyway and push updated commit. Thanks again. i should have caught the v10 thing on sass loader as i was just dealing with a similar issue on another project with that.
  • b
    please remove the webpack line as if nuxt updates the version of wp they use iit might become dnagerous
  • s
    ok
  • b
    We should probably start making pre-packaged plugins for the big frameworks soon
  • b
    Thanks for ironing out the details with us
  • s
    I can try to make one and add a PR, do you have a example i could look at to start learning/experimenting how to make one?
  • b
    We don't have any component-library plugins yet and the architecture/API is still in flux. Would you be interrested in helping us define it?
  • s
    Yes, anyway i can. I'm currently working on 2 large Nuxt based projects that i could try to experiment with. They both are re-builds of existing early vue apps. That is what got me digging so hard into testing/cypress....i wanted to make sure the new versions were more maintainable. How can i help?
  • b
    Let me ask above my head 😉
  • s
  • s
    Hi @User 🙂
  • s
    Hello
  • s
    The best way you can help is by using the project. If you've finished setting up and getting nuxt working, then just building your components inside of it is the best way to do it
  • s
    We also need to create more content and examples, so if you write blog posts or create example repos... that stuff is really valuable
  • s
    Essentially we need: QA, users, examples, and educational material
1...131415...37Latest