chalk | Intuitive package for prettifying terminal | Command Line Interface library

On top of my other answer, I'll add that everything is hackable nowadays. Is it an issue per-se? Not really since you're not really launching rockets.

Is it spooky? Yeah maybe because of how it sounds but at the end, if somebody in your company opens a phishing email you're exposed, so yeah: live your life and don't worry too much about it.

Also, a as reminder: every package that you install can be malicious at some point and during various steps. If you want a 100% bullet-proof codebase, you'll need to write everything yourself from bottom to top.

As has been commented in the comments section, the issue has been solved by moving the project folder outside the OneDrive directory.

Because it's a synchronized cloud folder, as soon as you install/add/delete/update anything, it's being updated in the OneDrive cloud so the file/folder it's being used in the background and potentially unreachable. If at this time you try to develop the project (gatsby develop or gatsby build) and the file is being used, you won't be able to run it.

I don't think it's a good practice to use a cloud folder because the amount of data synchronized (mainly because of the node_modules) it's something to care about (it's also ignored in the .gitignore for a reason) so moving it to any other folder outside the OneDrive directory should be enough to run your project because the rest of global dependencies, according to your logs, were successfully installed.

"node:" is an URL scheme for loading ECMAScript modules. As such it started for "import", not "require".

"node:process" is just an alternative name to load the built-in "process" module.

See also Node.js documentation - you can find the lowest supporting Node.js version inside the "History" tag (12.20.0, 14.13.1)

With newer Node.js it should be available for "require" as well (14.18.0, 16.0.0).

Some more details can be found here: node:process always prefers the built-in core module, while process could be loaded from a file.

It's happening because sizeof(words[27]) is giving the size of a pointer and words[27] is a pointer, and pointers have a fixed size of each machine, mostly 8 bytes on a x86_64 architecture CPU. Also, words is an array of pointers.

each of the character arrays occupy 8 bytes, including the character array "optimization".

No, each word in words is occupying a fixed memory (their length), 8 bytes is the size of pointer which is unsigned long int, it stores the address of the word in words.

It's common for third-party code to have type libraries of varying quality.

The particular module that you're importing is a JavaScript file (which does not include type information). However, there is a type declaration file accompanying it at https://deno.land/x/chalk_deno@v4.1.1-deno/index.d.ts.

Deno has a mechanism for cases like these, which allows you to provide a compiler hint for the module that you're importing: the @deno-types directive. Read about it here: https://deno.land/manual@v1.14.3/typescript/types#providing-types-when-importing

You can use it like this in your case, before the import statement:

The error above is because you're using the Common.JS module require syntax rather than the ES module import syntax.

Update:

https://github.com/luin/ioredis#running-commands-to-multiple-nodes

For starters, I'd prefer page.waitForSelector(yourSelector) over page.waitForNetworkIdle();. In most cases, it's a more direct guarantee that the data you want is on the page, whereas network idle can block waiting for all sorts of requests that are totally irrelevant to the data you're trying to scrape.

Some websites check the headers to block scrapers. You can try adding a user agent header as described in the Puppeteer GitHub issue Different behavior between { headless: false } and { headless: true } #665:

While forEach itself is not async-aware, that doesn't stop you from being able to push the asynchronous modification promises onto a list and awaiting for all of them at the end.