Publish NPM Packages & Automate with GitHub Actions

[@SeanCassiere]

Definiely a good starting point for a single package.
In my opinion, if you plan making this a serious package (like bindings for different frameworks or you want to modularize your library), you'd probably want your starting point to be a part of a monorepo (like with pnpm's built-in workspaces solution). From easily being able to write your documentation within the same repository or having example projects (like those that are runnable via stackblitz), having your starting point be a monorepo I've found to be quite blessing.

[@euanmorgann]

Return of the king 👑

[@Nedim-i7s]

Could u make episode 2 with Actions implementing code on EC2 instance and ECS/EKS?

[@johnkucharsky6927]

your package behave differently, Promise.all doesn't have this const promises = Object.values(data).map((fn) => fn());. Did you do this for purpose? It's convenient, but might be confusing. It's better to call functions like this: const second = async function () {
return "one";
};
const promiseObject = {
first: Promise.resolve({ p: 1 }),
second: second(),
third: Promise.resolve(true),
};

[@TomDoesTech]

@@johnkucharsky6927 I don't understand what the problem is