\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",[2893,2895,2896],{"name":2894,"color":2870},"$$",{"name":2872,"color":2873},{"name":2897,"color":2898},"A-writing-✍️","FBCA04",2671,"How we've migrated from yarn to pnpm","2023-05-18T11:23:54Z","https://github.com/kodadot/nft-gallery/issues/2671",0.7918767,{"description":2905,"labels":2906,"number":2917,"owner":2875,"repository":2876,"state":2877,"title":2918,"updated_at":2919,"url":2920,"score":2921},"\u003Cimg src=\"https://media4.giphy.com/media/ftAyb0CG1FNAIZt4SO/giphy.gif\"/>\r\n\r\nFinally, we have an endpoint we can start to integrate multi-chain components.\r\n\r\nAt some point would be nice to have some component which would wrap and abstract the current endpoint in case we find Supabase is not sufficient for our case. \r\n\r\n\r\n## Endpoint\r\nFollow up what can be done with new endpoint\r\nIf anyone wants to play with that here is the URL\r\n\r\n```\r\nhttps://xtnvtbdyvpbbnonbbcif.supabase.co/graphql/v1\r\n```\r\n\r\nYou need to add `apiKey` header into your request. You can find the key in the discord group.\r\n\r\n\r\nSample Query\r\n```graphql\r\nquery findCollections {\r\n\tcollectionsCollection(first: 10) {\r\n\t\tedges {\r\n\t\t\tnode {\r\n\t\t\t\tname\r\n\t\t\t}\r\n\t\t}\r\n\t}\r\n}\r\n```\r\n\r\n\r\n## Tasks \r\n- https://github.com/kodadot/nft-gallery/issues/4865\r\n- https://github.com/kodadot/nft-gallery/issues/4617\r\n- https://github.com/kodadot/nft-gallery/issues/4380\r\n- https://github.com/kodadot/nft-gallery/issues/4618\r\n- https://github.com/kodadot/nft-gallery/issues/4073\r\n- https://github.com/kodadot/nft-gallery/issues/4275\r\n- https://github.com/kodadot/nft-gallery/issues/4753\r\n\r\nOnce all the above done \r\n- https://github.com/kodadot/nft-gallery/issues/4379\r\n\r\n## Ref\r\n- https://developers.cloudflare.com/d1/platform/client-api/\r\n- https://github.com/kodadot/nft-gallery/issues/1824",[2907,2908,2910,2912,2915],{"name":2894,"color":2870},{"name":2909,"color":2873},"p2",{"name":2911,"color":2898},"A-search",{"name":2913,"color":2914},"chief","67EA1F",{"name":2916,"color":2898},"A-multi-chain",4257,"Enable Multi-chain capabilities in KodaDot","2023-03-15T14:49:24Z","https://github.com/kodadot/nft-gallery/issues/4257",0.7940701,{"description":2923,"labels":2924,"number":2933,"owner":2875,"repository":2876,"state":2934,"title":2935,"updated_at":2936,"url":2937,"score":2938},"I was long time skipping this but I guess hence will be transitioning to #584 Nuxt, we want to avoid as many dragons along the road. Thus having some testing suite would be more than welcome to keep some flow is present.\r\n\r\nIdeas for the testing framework we should use and why?",[2925,2926,2928,2931],{"name":2866,"color":2867},{"name":2927,"color":2873},"p4",{"name":2929,"color":2930},"intern","241540",{"name":2932,"color":2898},"A-tests",707,"closed","Introduce basic testing framework","2022-08-26T15:27:53Z","https://github.com/kodadot/nft-gallery/issues/707",0.7646923,{"description":2940,"labels":2941,"number":2944,"owner":2875,"repository":2876,"state":2934,"title":2945,"updated_at":2946,"url":2947,"score":2948},"currently we are at about 11min on ` Lint, Build & Test workflow`",[2942,2943],{"name":2909,"color":2873},{"name":2932,"color":2898},3841,"E2E - Cypress parallelization","2022-10-28T12:06:54Z","https://github.com/kodadot/nft-gallery/issues/3841",0.76577073,{"description":2950,"labels":2951,"number":2957,"owner":2875,"repository":2876,"state":2934,"title":2958,"updated_at":2959,"url":2960,"score":2961},"Our development pace is sometimes that fast ⏩ that once we add five new features, we wacky few usually working user flows, functions &c, usually css, position of 🔘 buttons or overall final outcome and manage unintentionally completely broke some primary functionality.\r\n\r\nThus I would like to nominate a few features and components we need to flex so I bet it would be gradually built what's and where needs to be done.\r\n\r\nThis issue is best fit for someone who would take care A-Z end to end tests, not just unit tests and can have follow ups issues once we find and fight some struggles. Hence KodaDot itself isn't any more few single lines of code and it's bit more complex, with more chains ⛓️ aggregation it will be better peace 🕊️✌️ mind to not break some stuff accidentally 😅\r\n\r\nRight now we have Cypress and Vitest as stack iirc, will update once got call w Viki\r\n\r\n# Ref\r\n- #1841 \r\n- #2948 \r\n- #2504 \r\n- https://github.com/kodadot/nft-gallery/issues/2964",[2952,2953,2955,2956],{"name":2894,"color":2870},{"name":2954,"color":2870},"$$$",{"name":2872,"color":2873},{"name":2932,"color":2898},2911,"Tests for critical functionality and evergreen components ","2022-08-05T13:04:33Z","https://github.com/kodadot/nft-gallery/issues/2911",0.77232563,{"description":2963,"labels":2964,"number":2968,"owner":2875,"repository":2876,"state":2934,"title":2969,"updated_at":2970,"url":2971,"score":2972},"Seems we've got positive reply https://github.com/netlify/netlify-plugin-nextjs/issues/759#event-5548942900\r\n\r\n> Hi. If you use Nuxt 3, or Nitro Bridge, SSR should work out of the box, with no plugin required. See this post for details https://www.netlify.com/blog/2021/10/12/nuxt-3-is-live-in-public-beta-and-ready-to-deploy-on-netlify-today/",[2965,2966],{"name":2927,"color":2873},{"name":2967,"color":2898},"A-nuxt",992,"Deploy nuxt ssr to Netlify ","2022-01-10T19:03:21Z","https://github.com/kodadot/nft-gallery/issues/992",0.77630484,{"description":2974,"labels":2975,"number":2981,"owner":2875,"repository":2876,"state":2934,"title":2982,"updated_at":2983,"url":2984,"score":2985},"Currently, there is this config, BUT would be perfect to abstract Netlify builds where Netlify serves to check if everything is OK!\r\n\r\nWith Github Actions as it's free, we don't need to pay for every build success or fail tho.\r\n\r\n### Actions to do\r\n- Configure Github Actions build as workflow, really basic one, just to tell us if stuff builds or not\r\n- Add to Renovate bot config `[skip ci]` to commit message https://docs.renovatebot.com/configuration-options/#commitmessage\r\n- Check if your Github Actions builds even there is `[skip ci]`\r\n\r\nhttps://github.com/kodadot/nft-gallery/blob/main/.github/renovate.json\r\n\r\n_Originally posted by @yangwao in https://github.com/kodadot/nft-gallery/issues/1500#issuecomment-1017718653_",[2976,2977,2978],{"name":2894,"color":2870},{"name":2909,"color":2873},{"name":2979,"color":2980},"v2.2","6AC658",1974,"Set Github Actions building","2022-01-27T12:56:00Z","https://github.com/kodadot/nft-gallery/issues/1974",0.7769131,{"description":2987,"labels":2988,"number":2993,"owner":2875,"repository":2876,"state":2934,"title":2994,"updated_at":2995,"url":2996,"score":2997},"We have quite big chunks loading upfront and would be great to move to Nuxt as the App is getting bigger and loads slower.\r\n### Requirements to keep. \r\n\r\n- [Docs](https://nuxtjs.org/docs/2.x/features/rendering-modes)\r\n- [ ] deployment through Netlify - simple keep it in jam stack as possible as we don't want to hustle servers, serverless is allowed :)\r\n- [ ] would we need to migrate to vercel or can we stick with Netlify? For sake avoid switching costs at the current stage.\r\n\r\n### What we will gain?\r\n- [x] faster load times\r\n- [x] better router?",[2989,2990,2991,2992],{"name":2866,"color":2867},{"name":2872,"color":2873},{"name":2929,"color":2930},{"name":2967,"color":2898},584,"Migrate KodaDot into Nuxt framework ","2021-11-09T11:57:42Z","https://github.com/kodadot/nft-gallery/issues/584",0.7838528,["Reactive",2999],{},["Set"],["ShallowReactive",3002],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fz5V5VQn3C5KtETUwvbSUd4KYnyunRInog8Sjdt9mTPk":-1},"/kodadot/nft-gallery/3679"]