![]() Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. 0 info it worked if it ends with okġ verbose cli '/usr/lib/inkdrop/resources/app/ipm/bin/node',ġ verbose cli '/usr/lib/inkdrop/resources/app/ipm/node_modules/npm/bin/npm-cli.js',ġ verbose cli '/home/caschbre/.config/inkdrop/.ipm/.ipmrc',ġ verbose cli '/home/caschbre/.config/inkdrop/.ipmrc',Ģ info using info using verbose npm-session 60ea352d31c970d4ħ http fetch GET 304 1197ms (from cache)Ĩ silly pacote remote manifest for fetched in 1203msĩ timing stage:loadCurrentTree Completed in 1216msġ1 silly install cloneCurrentTreeToIdealTreeġ2 timing stage:loadIdealTree:cloneCurrentTree Completed in 0msġ4 timing stage:loadIdealTree:loadShrinkwrap Completed in 1msġ5 silly install loadAllDepsIntoIdealTreeġ6 silly resolveWithNewModule checking installable statusġ7 http fetch GET 304 370ms (from cache)ġ8 silly pacote range manifest for fetched in 375msġ9 warn deprecated is no longer maintained and not recommended for usage due to the number of issues. It’s possible the issue is similar to another issue where core-js is the culprit, however that’s speculation on my part. The web clipper extension is failing to install. ![]() I installed inkdrop on a new computer and was attempting to install the same plugins I used on my other machine. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |