\u003Cbr /> \u003Cimg width=\"502\" alt=\"Screen Shot 2022-03-25 at 2 57 18 PM\" src=\"https://user-images.githubusercontent.com/734428/160080618-1320d0f9-5674-4133-9a57-9fd7f6e77ce2.png\"> | **3m** \u003Cbr />\u003Cbr /> \u003Cimg width=\"498\" alt=\"Screen Shot 2022-03-25 at 2 54 50 PM\" src=\"https://user-images.githubusercontent.com/734428/160080718-4f3fad38-71e5-4793-a839-797a0f87b65e.png\">\r\nInstall Deps in Actions | [1m 25s](https://github.com/kodadot/nft-gallery/runs/5676422402?check_suite_focus=true#step:4:35) | [**28s**](https://github.com/kodadot/nft-gallery/runs/5687650302?check_suite_focus=true#step:6:467)\r\n\r\n\r\nimpressive time savings.\r\nCurious if you would be keen to write an article on how we've migrated from yarn to pnpm? \r\nSome people might find it interesting as we are still early! \r\nThis morning found friends deciding between npm and yarn 😅.\r\n\r\nWe are usually publishing at https://medium.com/kodadot :)\r\n\r\nIssue is reserved for @preschian \r\n\r\n_Originally posted by @yangwao in https://github.com/kodadot/nft-gallery/issues/2643#issuecomment-1078864547_\r\n\r\n### Ref \r\n- https://medium.com/pnpm/why-should-we-use-pnpm-75ca4bfe7d93#:~:text=pnpm%20is%20not%20only%20faster,them%20from%20the%20global%20store.\r\n- https://rushjs.io/pages/maintainer/package_managers/\r\n- https://blog.logrocket.com/javascript-package-managers-compared/\r\n- [What does make pnpm special?](https://twitter.com/moo9000/status/1507297097070043184)\r\n- PNPM is the only option that solves the [NPM doppelgangers](https://rushjs.io/pages/advanced/npm_doppelgangers/) problem. In a complex monorepo, doppelgangers sometimes cause a lot of trouble, so PNPM has an important advantage in this regard.\r\n- we can push KodaDot logo to https://pnpm.io/users",[2892,2895,2897],{"name":2893,"color":2894},"$$","0E8A16",{"name":2896,"color":2883},"p3",{"name":2898,"color":2880},"A-writing-✍️",2671,"How we've migrated from yarn to pnpm","2023-05-18T11:23:54Z","https://github.com/kodadot/nft-gallery/issues/2671",0.7823796,{"description":2905,"labels":2906,"number":2909,"owner":2868,"repository":2869,"state":2870,"title":2910,"updated_at":2911,"url":2912,"score":2913}," Hmm, I think the limited specs of the current runner cause flaky tests from e2e. Since running e2e tests is quite heavy, we need to increase the specs: https://docs.github.com/en/actions/using-github-hosted-runners/about-larger-runners/about-larger-runners\r\n\r\n_Originally posted by @preschian in https://github.com/kodadot/nft-gallery/issues/10713#issuecomment-2262346093_\r\n ",[2907],{"name":2908,"color":2880},"A-tests",10714,"E2E: Flaky tests","2024-08-01T08:24:35Z","https://github.com/kodadot/nft-gallery/issues/10714",0.7886196,{"description":2915,"labels":2916,"number":2923,"owner":2868,"repository":2869,"state":2924,"title":2925,"updated_at":2926,"url":2927,"score":2928},"I guess switching to pnpm from yarn it seems from cached they do amazing work but on the first time they take quite a long time to build\r\n\r\nNow\r\n> Build time: 6m 3s. Total deploy time: 6m 7s\r\nhttps://app.netlify.com/sites/koda-nuxt/deploys/62403dedcfa58900095b76d1\r\n\r\nBefore\r\n> Build time: 4m 5s. Total deploy time: 4m 9s\r\nhttps://app.netlify.com/sites/koda-nuxt/deploys/6239dbdd27c5220009cec772\r\n\r\nthis is quite scary lol \r\n> 3:34:06 PM: Finished processing build request in 10m39.002735083s\r\n\r\n### Ref\r\n- #2692 ",[2917,2919,2920],{"name":2918,"color":2894},"$",{"name":2896,"color":2883},{"name":2921,"color":2922},"🧙♀️ - bug-hunt","DC2653",2696,"closed","pnpm builds taking on first time quite long ","2023-03-01T19:12:53Z","https://github.com/kodadot/nft-gallery/issues/2696",0.7333144,{"description":2930,"labels":2931,"number":2938,"owner":2868,"repository":2869,"state":2924,"title":2939,"updated_at":2940,"url":2941,"score":2942},"I've noticed that sometimes builds now last like for 7-10m, on average 7minutes +\r\nOn average we've been somewhere between 4-5m. \r\n\r\nbefore\r\n\u003Cimg width=\"1190\" alt=\"image\" src=\"https://user-images.githubusercontent.com/5887929/172619410-6c49c078-24fa-40fb-9670-e4d801ee60f6.png\">\r\n\r\nnow\r\n\u003Cimg width=\"1179\" alt=\"image\" src=\"https://user-images.githubusercontent.com/5887929/172622256-496624d3-11db-4a0f-bae7-3c5201f1c224.png\">\r\n\r\n\u003Cimg width=\"1137\" alt=\"image\" src=\"https://user-images.githubusercontent.com/5887929/172622319-6f6293e8-7fca-4e1e-b2b0-f3af506c8b11.png\">\r\n\r\n\r\n",[2932,2933,2935],{"name":2918,"color":2894},{"name":2934,"color":2883},"p4",{"name":2936,"color":2937},"performance","922478",3123,"Seems build times take a while on beta ","2023-10-11T11:07:28Z","https://github.com/kodadot/nft-gallery/issues/3123",0.7464039,{"description":2944,"labels":2945,"number":2954,"owner":2868,"repository":2869,"state":2924,"title":2955,"updated_at":2956,"url":2957,"score":2958},"As started in\r\n- nuxt/framework#2911\r\n\r\nI was unsuccessful to implement cypress as GH action / Netlify plugin, we got the tests available to run locally right now, but the ultimate idea is to move this into automated thing which will run with every PR. @preschian you look like an ideal candidate for this one and it would help us a lot 👀 \r\n\r\nNot sure if any of these references help:\r\n\r\n- https://github.com/cypress-io/netlify-plugin-cypress\r\n- https://docs.cypress.io/guides/continuous-integration/github-actions",[2946,2949,2950,2953],{"name":2947,"color":2948},"enhancement","a2eeef",{"name":2918,"color":2894},{"name":2951,"color":2952},"p1","D93F0B",{"name":2908,"color":2880},3679,"Connect Cypress tests into CI/CD pipeline","2023-01-19T17:35:30Z","https://github.com/kodadot/nft-gallery/issues/3679",0.74647826,{"description":2960,"labels":2961,"number":2966,"owner":2868,"repository":2869,"state":2924,"title":2967,"updated_at":2968,"url":2969,"score":2970},"E2E test needs to be extended to cover mobile as well. I'll start working on this, but first thing we'll need to solve to avoid bloating the test time further is:\r\n\r\n- #3841 \r\n\r\n",[2962,2965],{"name":2963,"color":2964},"chief","67EA1F",{"name":2908,"color":2880},3965,"E2E - Mobile version","2023-12-20T11:01:34Z","https://github.com/kodadot/nft-gallery/issues/3965",0.75968826,{"description":2972,"labels":2973,"number":2979,"owner":2868,"repository":2869,"state":2924,"title":2980,"updated_at":2981,"url":2982,"score":2983},"Kindly reminder for us we've passed our free plan and time to evolve and get a paid plan.\r\nMeanwhile, good hints are how to optimize our bundle as it takes quite a lot to process.\r\nhttps://answers.netlify.com/t/support-guide-how-can-i-optimize-my-netlify-build-time/3907",[2974,2977,2978],{"name":2975,"color":2976},"good first issue","5319e7",{"name":2918,"color":2894},{"name":2882,"color":2883},279,"Optimize builds - Over build minutes on Netlify","2022-04-08T09:45:29Z","https://github.com/kodadot/nft-gallery/issues/279",0.75988126,{"description":2985,"labels":2986,"number":2994,"owner":2868,"repository":2869,"state":2924,"title":2995,"updated_at":2996,"url":2997,"score":2998},"It's a bit frustrating every time I need to clear the cache between new changes in deploy previews, even I see on `main` branch stuff which isn't there tho 😅 \r\n\r\nHas someone will figure out the current caching issue to really flush stuff browser cache? \r\nIn future, it would help to avoid unnecessary caching issues on the client browser while testing new stuff.\r\n\r\n\r\n",[2987,2988,2990,2993],{"name":2918,"color":2894},{"name":2989,"color":2883},"p2",{"name":2991,"color":2992},"experimental","B09211",{"name":2921,"color":2922},2237,"Time to tackle cache more efficiently ","2022-08-25T16:58:22Z","https://github.com/kodadot/nft-gallery/issues/2237",0.7751835,["Reactive",3000],{},["Set"],["ShallowReactive",3003],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$flziEDT89rnnQybQmUg--jREjj2D-OBjpAQ-wrsOf85g":-1},"/kodadot/nft-gallery/3841"]