Echo JS 0.11.0

I think that it's of some value for libraries... the definitions file(s) for use with VS Code are really nice, even when using plain JS in your end project.

Inside some projects, it may or may not provide value, as TFA mentions, there's no io checks to/from APIs.  Beyond this, it doesn't negate the need for testing and coverage.  In some scenarios, type complexity can be a lot of effort for very little gain.

Aside: I've been looking at some of the GraphQL libraries with great interest... though I'm unsure of pieces of authentication and updates, it's definitely a nice approach to certain types of data and workflows and does (optionally depending on library) do type checking against definitions.

Personally, I don't support any version of IE at this point.  It's EOL, replaced and a security risk.  Not to mention the shims/shivs/transforms needed for ES2017+ are massive.  It's a  target that's not worth taking for the most part.

Another use case worth mentioning is creating reports from HTML/SVG/Canvas output to PDF for download.  It's compute heavy, but often easier than trying to shoe-horn a reporting module, or use PDF primitive libraries directly.

I'm not sure what "at Free" means in this context, doesn't seem to be any kind of service or relevance here.

Beyond this, for node/typescript projects, generally speaking, you should use a .dockerignore file to exclude the things that shouldn't be copied into the container.  From there, you should use multi-stage containers for your build pipeline... copy the entire project/solution or set of projects into a start or source container, then setup build containers for each portion (client, server, etc) and a final runtime container exposed for deployment.

Please don't post for every single release if it's less than a few weeks from a prior post.  If you are posting for a specific release, you should link to the release page and/or release notes specifically.

dotenv is *NOT* meant to be used this way...

Generally speaking, do *NOT* commit your environment configurations (other than local development) to source control, you do *NOT* want variance in your configuration files, this is a deployment issue.

What you should do, is add `.env` to your .gitignore file so it doesn't get committed.  You may want to add a `.env.dev.env` to source control with typical local settings.  The dev env file should have a comment that you should copy it to a plain `.env` file for local development.  You should also consider having fallback options in your configuration module, that represents the dev or production defaults as much as reasonable.  ONLY load `.env` not ENVIRONMENT.env

Advice, load the .env file before loading any other modules, do it all synchronously, or an async load of your modules after environment and configuration are loaded.  I would advise searching upward at least 2-3 directories for the .env then change your working directory to where the .env file is... for a static (non-container) deployment, this allows you to setup your .env in a parent directory from your application, and relative paths should work properly.

For containerized (docker) deployments, you should set the environment as part of your start/deployment model.  Kubernetes, Dokku and other orchestration environments have options for this, you shouldn't deploy a .env file inside a container, and generally it should be mostly for development and/or static deployments.

Aside: you may, if using CI/CD for static deployments, want to use a `.env.template.env` file for transformation as part of your deployment model.

It's still prototype based inheritance with all the negatives... the syntax is sugar and sometimes nice, but should generally favor other patterns for performance.

I'm so meh on ORMs, especially in scripted languages, I understand this is TypeScript, but all the same.

If I'm going to take the time to really lay out all of the boilerplate needed for an ORM, I think I'd just assume go the extra step for GraphQL.  There's even a similar typescript library for this[1].

[1] https://typegraphql.ml/docs/introduction.html

Nice... usually when I see more than 3 upvotes on an article, it's either pretty good/useful or spam.  Glad it's the former.

Not sure I'd use storeon over redux in anything resembling a complex app though... there's value in the module system.  Though, you could probably just copy and tweak as needed for the size of the main store, and use the rest with it.

Similarly, although I find other react-alikes interesting, the feature parity isn't there and real world performance isn't that impacted vs. having the extra dev support in react.

TailwindCSS does look interesting, it seems to be a bit more specialized than say Bootstrap + SASS, that said, I've been leaning into more prescriptive components (material-ui), and while I do find the need to customize, I like what JSS provides in that space.

If this were 6+ years ago, before React, I'd probably favor tailwind... now I favor components.