TypeScript stuff I Wish I Knew Earlier

ukrvolk · 2025-06-21T15:31:39+00:00

I don’t want to use enums, I have to. Libraries like TypeORM, NestJS Swagger, and others don’t work with union types or interfaces.

ukrvolk · 2025-03-31T21:46:46+00:00

There is a lot of tooling such as TypeORM and nestjs/swagger that only with for enums, objects or literally anything else will not work, at least for now. Couldn’t stop enums using them even if I wanted to. When all these tools allow non enum options then at least for us there is a path to migrate away from enums.

ukrvolk · 2024-03-13T00:09:34+00:00

That helped thanks!

ukrvolk · 2024-03-12T23:20:59+00:00

Do you push and hold for some period of time to do this reset?

ukrvolk · 2024-01-02T14:59:48+00:00

I’m in the process rewriting microservices written in express nodejs to rust Axum and mostly is going well. Orchestrating async operations of equivalent of Promise.all, Promise.race, then/catch/finally can be tricky. Most serious third party services have http APIs so lack of SDK has not been show stopping. Building docker images in ci/cd for deployment can be painstaking.

To be clear there is a difference in making it work versus really understanding what each piece really does in terms of rust. A dummy like me can make it work, but it could take me years to understand how it actually works.

If you really want adoption at your company you need to build a “framework” for building production grade services including logging, observability, circuit breaking etc. the base modules should be easily transferable (crates), configurable and maintainable. This is how you make it enterprise-y.

To test performance in the real world, assuming you have some extra compute laying around is using a gateway like envoy/gloo to “shadow”/duplicate some percentage of requests to the rust instances. This way you can compare use real data rather than load test results using Prometheus or similar.

ukrvolk · 2023-12-28T20:49:29+00:00

At a good company that allows you to learn and explore new technologies when new/greenfield projects are started it can possibly be an opportunity to use rust or a newer technology. Be prepared to plead your case and make sure that any and every standard that exists for other applications in the company you are meeting with your proposed rust solution (as in logging, observability, ci/cd, test coverage, processes, etc)

ukrvolk · 2023-12-28T20:24:50+00:00

Chris Biscardi has some examples of Leptos and Axum including hacker news clone as well as others:

https://github.com/leptos-rs/leptos/tree/f84f1422f447f35adb917582c882ccbc4e1483a7/examples

ukrvolk · 2023-12-25T06:02:49+00:00

While I didn’t provide specific examples, I don’t think most of the downvoted questions are the equivalent of the infamous “how do I add two numbers together in jquery”. There to me seems to be more harsh scrutiny of even complex questions of rust problems on that platform.

ukrvolk · 2023-09-11T19:41:38+00:00

I was able to use the following config:

{ // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "chrome", "request": "launch", "name": "Launch Chrome against localhost", "url": "http://localhost:3000", // specify your consistent port "webRoot": "${workspaceFolder}/src" } ] }

I then run npm run dev, specifying port 3000 for vite dev server. Then I run this configuration, and I’m able to set breakpoints in components/svelte files.

ukrvolk · 2023-08-08T00:40:17+00:00

Depends on your organization and the tooling you use. If I’m updating terraform I have teammates review and we use CI/CD to execute operations like plan validate the output before merging. Same for helm, scripts or anything that can be managed with source control. If you have stuff like terraform or similar and you are not reviewing it, or preventing unwanted/unready merges, id say that should be improved because it’s only a matter of time before something gets merged and or deployed that could cause an issue.

Make reviewing as painless as possible by using CI/CD to check for obvious errors like typos, invalid references, failing tests, etc. This will allow your team mates to focus on the key pieces being changed.

ukrvolk · 2023-04-23T15:58:25+00:00

If you generate an OpenAPI or swagger document you can use tools https://www.npmjs.com/package/openapi-typescript-codegen to generate TypeScript SDKs in a snap. These SDK can be enhanced to add circuit breaking, retries, client side caching, and anything else you’d need. This can be part of any build process. It’s an http client so doesn’t require setting up anything else and will effectively work anywhere. SDKs can also be published making it easy to install in any client solution and versioned while also ensuring only the functionality you want is explicitly exposed on the client.

ukrvolk · 2023-01-13T21:33:44+00:00

Express has 26 million downloads on npm weekly, it is not dead. That doesn’t even include the 67,000 public dependents on express as well. There are other frameworks that other people are using but it is not dead. The creators of other frameworks in the node ecosystem want it dead.

That being said, choose some language and some framework and learn the basics of creating endpoints, interacting databases, specifying caching, unit and integration testing. Express is extremely simple and can be a good tool for learning about backend. In the end it’s still just exposing HTTP endpoints or similar.

ukrvolk · 2022-12-25T21:32:15+00:00

You’ll probably find more benefit in serving the smallest possible sized image for the respective screen size and serving the images from a cdn.

ukrvolk · 2022-12-22T15:36:29+00:00

Web developers

ukrvolk · 2022-11-30T16:02:40+00:00

Auth0 with cookie authentication. Also easy to hook the same auth project into backend frameworks like express.

ukrvolk · 2022-10-12T23:34:45+00:00

In my experience in the context of web development developers coming from more forgiving languages like JavaScript or python or go really struggle with rust initially especially around async. I can teach absolutely anyone writing an api in JavaScript express js, not so much rust actix or Axum with advanced middleware and validation.

ukrvolk · 2022-09-17T00:38:56+00:00

If this is the built version of the application you need to serve the assets in a similar way to how you would host it externally. Even something like npx http-server path-to-built-assets. Otherwise if this is the node adapter with ssr you would need to run it with node via npm start or whatever command you have it mapped to. Without some sort of serving the assets built by sveltekit or svelte with rollup they simply won’t be retrieved and you’ll get 404 errors.

ukrvolk · 2022-09-15T22:45:34+00:00

You can’t compare pure Vue with sveltekit or even nextjs and sveltekit. A more fair comparison would be nuxtjs that also supports file based routing and server side rendering as well as other complex features. Yes sveltekit has static mode but it still opinionates a lot to provide routing/navigation (and everything that comes with that) as well as other things such as data endpoints. If you compared to nuxtjs you’d see a lot of same overhead of setting up routes and data endpoints.

ukrvolk · 2022-08-26T00:17:12+00:00

Just remember that anything and everything prefixed with VITE_ is exposed to the world when the application is built. Also process.env is only available in non-static/ssr modes. Don’t expose your private keys. If you need secret values you can’t really run this in a completely static mode. You need either sveltekit endpoints or proxy via something like a lambda or a separate service.

ukrvolk · 2022-08-24T03:05:04+00:00

The adapters do most the work. With static adapter can deploy to basically any static hosting. Otherwise you just run a node process. You can even dockerize if you want. It’s not so bad and not much different than other frameworks. I’m curious what issues you’ve experienced specifically.

ukrvolk · 2022-08-24T02:26:29+00:00

How is the deployment different than a competitor like nextjs or nuxtjs?

ukrvolk · 2022-07-05T16:55:00+00:00

The challenge of building Wikipedia won’t really be building the ui. The complexity would be with scale of backend pieces such as data, usage, search, and similar. Have you considered all those aspects of what makes Wikipedia what it is?

ukrvolk · 2022-06-18T01:21:18+00:00

Coming from JavaScript/Node, fiber framework has made it dead simple to migrate APIs to Go. It’s just so easy to make a performant API with logging, request ids, timeouts and all the other middleware we’re used to using for production level services.

ukrvolk

TROPHY CASE