\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",[2875,2878,2881],{"name":2876,"color":2877},"$$","0E8A16",{"name":2879,"color":2880},"p3","D4C5F9",{"name":2882,"color":2883},"A-writing-✍️","FBCA04",2671,"nft-gallery","How we've migrated from yarn to pnpm","2023-05-18T11:23:54Z","https://github.com/kodadot/nft-gallery/issues/2671",0.78229445,{"description":2891,"labels":2892,"number":2893,"owner":2865,"repository":2866,"state":2867,"title":2894,"updated_at":2895,"url":2896,"score":2897},"We don't use that anymore:\r\n\r\n- https://github.com/kodadot/nft-gallery/issues/4597",[],19,"Deprecate durable object","2023-01-06T16:19:52Z","https://github.com/kodadot/workers/issues/19",0.79053193,{"description":2899,"labels":2900,"number":2909,"owner":2865,"repository":2885,"state":2910,"title":2911,"updated_at":2912,"url":2913,"score":2914},"It seems after the update of \r\n- #4713 \r\n\r\nit doesn't update the client anymore. \r\nI did not get any new toast, or at least I still have on https://beta.kodadot.xyz all languages \r\nyet when I open it in incognito, I see only a new one \r\n\r\ncurrent state\r\n\r\n\r\nincognito \r\n\r\n\r\nI guess it's because it doesn't generate proper sw.js ? service worker where old instance was listening? \r\nedit seems is there, old one doesn't switch for new one?\r\n- https://beta.kodadot.xyz/sw.js\r\n\r\n\r\n\r\n## Documentation\r\n\r\nProbably needs custom workbox service worker? \r\n\r\n- https://github.com/kevinmarrec/nuxt-pwa-module\r\n\r\n- https://github.com/kodadot/nft-gallery/blob/main/nuxt.config.js#L246 🤔\r\n\r\n## Ref \r\n- #4723 \r\n\r\n",[2901,2904,2906],{"name":2902,"color":2903},"bug","d73a4a",{"name":2905,"color":2877},"$",{"name":2907,"color":2908},"p1","D93F0B",4727,"closed","service worker / pwa fetch new update doesn't show up","2023-01-17T10:46:03Z","https://github.com/kodadot/nft-gallery/issues/4727",0.73469585,{"description":2916,"labels":2917,"number":2927,"owner":2865,"repository":2885,"state":2910,"title":2928,"updated_at":2929,"url":2930,"score":2931},"I've just had an occasion where toast came, clicked X, fetched a new version and collection links on collections view stopped working... then I opened a new window for beta.kodadot.xyz and their collections have worked.\r\n\r\nNot sure what witchcraft is here, but I sense that service worker, pwa, cache reload doesn't work as intended should be.\r\nIt's quite hard to test out stuff but just raising awareness that we have this kind of glitches here and there and that's bit no go for production.",[2918,2919,2921,2924],{"name":2907,"color":2908},{"name":2920,"color":2883},"A-nuxt",{"name":2922,"color":2923},"🧙♀️ - bug-hunt","DC2653",{"name":2925,"color":2926},"v2.2","6AC658",1510,"Reimplement Service worker and cache ","2022-03-25T12:34:50Z","https://github.com/kodadot/nft-gallery/issues/1510",0.74110156,{"description":2933,"labels":2934,"number":2940,"owner":2865,"repository":2885,"state":2910,"title":2941,"updated_at":2942,"url":2943,"score":2944},"We need to have service worker to update clients once there is new version available \r\n\r\n@dezine2dev will check on this for #843 \r\n\r\nhttps://pwa.nuxtjs.org/setup\r\n\r\nCurrent https://beta.kodadot.xyz \r\n\r\n\r\nhttps://kodadot.xyz looks like this\r\nCurrent \r\n\r\n",[2935,2936,2937],{"name":2879,"color":2880},{"name":2920,"color":2883},{"name":2938,"color":2939},"koda2","AB66CA",984,"Add service worker for Nuxt","2021-11-30T13:17:45Z","https://github.com/kodadot/nft-gallery/issues/984",0.74981683,{"description":2946,"labels":2947,"number":2948,"owner":2865,"repository":2885,"state":2910,"title":2949,"updated_at":2950,"url":2951,"score":2952},"Apparently, Netlify has changed something https://nft.kodadot.xyz/robots.txt?__WB_REVISION__=b6216d61c03e6ce0c9aea6ca7808f7ca\r\n\r\n\r\n\r\nFigure out netlify.toml would be helpful ",[],196,"Broken service worker which might broke updates on clients?","2021-03-22T14:13:27Z","https://github.com/kodadot/nft-gallery/issues/196",0.7557723,{"description":2954,"labels":2955,"number":2964,"owner":2865,"repository":2885,"state":2910,"title":2965,"updated_at":2966,"url":2967,"score":2968},"Hence there were unknown changes or at least on Basilisk we've noticed that after fresh minting things are not working. \r\nThus time to revisit the initial implementation of cf workers and how we have it in the current state.\r\n\r\nCurrently, the user pins stuff on Estuary, which we've found acting suboptimal as it's being stored on Filecoin (archive nodes(?) and retrieving through pinata gateway takes a long time (peering issues?). (Something has changed outside of our control, we are investigating, it till we are looking to mitigate it and make a more resilient and antifragile scenario) \r\n\r\n### Future proposed changes are \r\n- [x] #3358 temp hotfix\r\n- [ ] Pinning metadata on Pinata (as we are blazingly fast here for end-user experience) and rest pinning could be kept on Estuary -> We are pinning rn on NFT.storage and seems temporary hotfix is okay\r\n- [ ] At minting, we should push media to CF images (might not happen during BSX mints?)\r\n- [ ] At the new implementation, we would doesn't need durable objects at all and fetch images by IPFS hash from CF images to accelerate end-user experience while they browsing collections/explorer\r\n- [x] https://github.com/kodadot/nft-gallery/issues/3745\r\n- [x] https://github.com/kodadot/nft-gallery/issues/3296\r\n\r\n### Long-term goal\r\n\r\nCurrently, we are fairly doing close to 1TB on Pinata Gateway monthly as transfers for users and this would be an interesting way to offload as public goods for storage providers, like those around the Filecoin provider's circle\r\n\r\n### Suggested would be to recycle code from\r\n- https://github.com/kodadot/nft-gallery/blob/main/src-functions/pinJson.js \r\n- https://github.com/kodadot/workers/blob/master/pinning/src/lib.rs#L84\r\n\r\nTo make it work with Pinata directly from workers to pin JSON metadata there\r\n\r\nCheck the links below for more context \r\nLet's comment below if you want to thrill on this issue \r\n\r\n### Ref\r\n- https://github.com/kodadot/packages/issues/17\r\n- https://github.com/kodadot/workers/issues/7\r\n- https://github.com/kodadot/workers/issues/8\r\n- https://github.com/kodadot/nft-gallery/issues/3253\r\n- https://github.com/kodadot/bao/issues/10",[2956,2957,2959,2961],{"name":2876,"color":2877},{"name":2958,"color":2880},"p2",{"name":2960,"color":2883},"A-basilisk",{"name":2962,"color":2963},"chief","67EA1F",3334,"Rework current pinning & storage strategy","2023-02-08T11:21:12Z","https://github.com/kodadot/nft-gallery/issues/3334",0.76391184,{"description":2970,"labels":2971,"number":2976,"owner":2865,"repository":2885,"state":2910,"title":2977,"updated_at":2978,"url":2979,"score":2980},"Someone can take care and migrate to yarn v2, it should cut us time for development and fresh installs \r\n\r\nWhy we should migrate -> https://yarnpkg.com/getting-started/qa#why-should-you-upgrade-to-yarn-modern\r\n\r\nNote to @yangwao -- check deployments if works ok!\r\n- on beta\r\n- on production\r\n\r\n### Ref\r\n- https://yarnpkg.com/getting-started/migration",[2972,2973,2974,2975],{"name":2905,"color":2877},{"name":2876,"color":2877},{"name":2879,"color":2880},{"name":2925,"color":2926},2197,"Migrate to the newer package manager","2022-03-25T16:16:26Z","https://github.com/kodadot/nft-gallery/issues/2197",0.7771792,{"description":2982,"labels":2983,"number":2987,"owner":2865,"repository":2885,"state":2910,"title":2988,"updated_at":2989,"url":2990,"score":2991},"### What happened?\n\nA \"_(node:7469) [DEP0148] DeprecationWarning_\" warning appears in terminal immediately the builder initialized\n\n### Please reproduce in steps\n\nNavigate to the project folder and start the project\r\n```bash\r\ncd nft-gallery\r\nyarn dev\r\n```\r\nThen watch the terminal for this error.\n\n### Expected Behavior\n\nThe server should start with no error.\r\n\r\n> You may find https://github.com/jaydenseric/extract-files/issues/17#issuecomment-847026136 and [Package entry points](https://nodejs.org/api/packages.html#package-entry-points) helpful.\n\n### What browsers are you seeing the problem on?\n\n_No response_\n\n### Are you logged in?\n\n_No response_\n\n### At which address did you encounter bug?\n\n_No response_\n\n### Screenshots\n\n\n\n### Relevant log output\n\n_No response_\n\n### Code of Conduct\n\n- [X] I agree to follow this project's Code of Conduct",[2984,2985,2986],{"name":2902,"color":2903},{"name":2905,"color":2877},{"name":2958,"color":2880},2243,"DEP0148 - update this package.json to use a subpath pattern like \"./*\"","2022-08-27T09:24:30Z","https://github.com/kodadot/nft-gallery/issues/2243",0.77737886,["Reactive",2993],{},["Set"],["ShallowReactive",2996],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fe2L7ftJ-S8aes2CChlCtNjxUHajBXIsW84TaqmQ0GfY":-1},"/kodadot/nft-gallery/1797"]