DEV Community: inversemetric

Missing: Universal Watch Mode

inversemetric — Tue, 12 May 2020 14:20:44 +0000

Having a tight feedback loop for development is essential. At some point, tools like nodemon, hot module reloading, and even codepen gave us the ability to immediately see the results of the code we write.

The problem is that every tool does it differently, so you have to look it up for each case whether it's from react, vue, angular, webpack, parceljs, typescript, python, haskell, java, jest, jasmine, karma, mocha, nyc, gulp, bash...

What would it take to get everyone using one solution for this?

Kubernetes CI/CD - my experience

inversemetric — Tue, 12 May 2020 05:17:06 +0000

Kubernetes has been fun to learn!
EXCEPT for CI/CD.

Here's some constructive criticism: Out of all the tools I've tried, they all have such awful developer experience, that after weeks of failed attempts I chose to build my own CI/CD server which I run on my local machine using github webhooks, ngrok, and a thin koa server that runs commands for me.

So far I've tried:

Jenkins X
Jenkins
GoCD
Flux
Brigade
Keel
Spinnaker
GitKube

Maybe it's the fact that I insist on never downgrading from Helm 3, or some of the tools are pretty fresh, but as a developer wanting to get my idea to market, I just don't have time to mess with tools that take multiple days to understand or set up.

I'm writing this as feedback, because I don't think I'm the only one. Something else that desperately needs addressed is that docker in docker doesn't just automatically work for building images, which may have contributed to my failed experiences with the tools above.

Same Dockerfile for Production and Development

inversemetric — Tue, 12 May 2020 05:02:19 +0000

You want your servers to run on docker and you want a consistent developer experience locally.

Great!

In your Dockerfile, COPY your source files as normal.
Create a docker-compose.yml file that mounts a volume from the host machine to the source directory (overriding the COPY from the dockerfile). Override the command inside docker-compose.yml as needed.

Build normally for production.
Use docker-compose up --build for development on your host machine.

Example:

Dockerfile

FROM node:alpine
WORKDIR /api
COPY package.json .
COPY yarn.lock .
RUN yarn install
COPY . /api

CMD ["node", "src/index.js"]

docker-compose.yml

version: '3.6'
services:
  api:
    build: .
    volumes:
      - ./src:/api/src
    command: npx nodemon src/index.js

create-react-app component library mode

inversemetric — Thu, 12 Dec 2019 15:00:57 +0000

How, after all these years, does create-react-app not have a "component library" mode?

It's been a huge pain point for a lot of people for a long time

That's why there are a ton of libraries and articles about how to do it, which are drastically different from one another.

All it needs is this
• Full endorsement from the react team
• Use the same webpack configuration as create-react-app
• ...Except the entrypoint needs to NOT have a hash in the js filename

What doesn't work
• Anything built on rollup, because it's not the same configuration
• Anything that's "manual" because it will have to be manually updated by the author when cra updates
• Anything that doesn't have community support because no one new can find it (terrible developer experience)