metascraper VS patch-package

Yep but there is a fallback to metascraper [0] which does check the HTML tags. However the fallback didn't work in case GPT returns a 1970 date -- I just fixed this! [1]

I think you can now remove the date from your post content and it should still work. If you submit your website again it should do a re-scrape if you changed the content text. Thanks for catching this :)

[0] https://metascraper.js.org/#/

[1] https://github.com/lindylearn/aboutideasnow/commit/8b0ea5b46...

200 {description: 'easily scrape metadata from an article on the web.', publisher: null, title: 'metascraper, easily scrape metadata from an article on the web.', url: 'https://metascraper.js.org'} [[Prototype]]: Object

I am using this library https://github.com/microlinkhq/metascraper but it doesn't catch it.

First of all, we'll use the got npm package to fetch the website content (feel free to use any other fetching library), and the metascraper npm package to extract the metadata:

> After that, pricing starts at $25 per month for up to 15,000 requests.

This is very expensive for any decent usage. I have used tools like metascraper for this purpose and it worked pretty well. Setup just requires throwing a tiny nodejs app on a raspberry pi or $5 server and that can handle tons of requests.

https://github.com/microlinkhq/metascraper

In order to allow users to use their device as a controller to adjust the position of the camera and find stars, I use the depreciated DeviceOrientationControls by patching it back into Three. In order for DeviceOrientationControls to function, we need access the user to grant access to their device's orientation. I attempt to gain access to this, alongside their camera, during a previous step of the UX using a custom composable I wrote for this purpose. You can see that permission step in the mockup video above. Once this permission is granted, we can initialize our DeviceOrienationControls with a single line.

If you use Yarn, there’s the `yarn patch` command [1], which lets you maintain patches for your dependencies. Even though I try to upstream patches wherever possible, sometimes you just want to apply a quick patch and move on, especially if the dependency is poorly maintained or even worse, deeply nested in your dependency hierarchy. I use `yarn patch` regularly, it’s one of the main reasons why I moved to Yarn in the first place.

If you’re not using Yarn, there seems to be a similar thing on npm, `patch-package`. [2] I never had to use that though.

[1]: https://yarnpkg.com/cli/patch

[2]: https://www.npmjs.com/package/patch-package

You can use patch-package to edit the part of the library.

patch-package

NPM doesn't have a patch command, but you can use patch-package to achieve the same result.

If there's issue ticket discussing it and someone can fix it, ask for patch file and use patch-package to patch it

You can try this (I highly recommend you to use the Patch Package library to track changes on any external library that you are using. (https://www.npmjs.com/package/patch-package)