I write about the things I learn in the Frontend ecosystem. Most of them are about Next.js and React.
You can find some of my thought pieces on my blog: (https://meje.dev/blog)
I just hate complicated compatibility issues. If they want to run node programs directly, they can use something like vite-node/tsx/esno/esm and those tools will handle it automatically. If it's a web program, which now almost certainly goes through a build tool, that's not a problem anymore.
I also wrote an article introducing dev.to/rxliuli/developing-and-buil...
I write about the things I learn in the Frontend ecosystem. Most of them are about Next.js and React.
You can find some of my thought pieces on my blog: (https://meje.dev/blog)
I write about the things I learn in the Frontend ecosystem. Most of them are about Next.js and React.
You can find some of my thought pieces on my blog: (https://meje.dev/blog)
For local testing the final, published package you can use verdaccio as a local npm registry. This way it is possible to test it like a real package with installation.
I write about the things I learn in the Frontend ecosystem. Most of them are about Next.js and React.
You can find some of my thought pieces on my blog: (https://meje.dev/blog)
Why not have the package have a dependency for styled-components? Instead of having the user install the dependency, even if they don’t use it directly. Also, you pre-build the styles, why would the user need the styled components library at all, at that point?
I write about the things I learn in the Frontend ecosystem. Most of them are about Next.js and React.
You can find some of my thought pieces on my blog: (https://meje.dev/blog)
We are now only compatible with esm, and all construction is done based on vite, and even wrote a vite plug-in for it to specifically support it.
ref: npmjs.com/package/@liuli-util/vite...
Oh, wow! This feels promising!
What about people who tend to bend towards the commonjs side of things?
I just hate complicated compatibility issues. If they want to run node programs directly, they can use something like vite-node/tsx/esno/esm and those tools will handle it automatically. If it's a web program, which now almost certainly goes through a build tool, that's not a problem anymore.
I also wrote an article introducing
dev.to/rxliuli/developing-and-buil...
Oh! Nice! I get your point now.
Everything supports ESM now, excepts sticks in the mud.
Ah! That's great to hear Tbh!
Good article!
For local testing the final, published package you can use verdaccio as a local npm registry. This way it is possible to test it like a real package with installation.
Oh wow! Thank you so much for suggesting this. I'll definitely give it a try when next I'm working on something
Or Yalc
Why not have the package have a dependency for styled-components? Instead of having the user install the dependency, even if they don’t use it directly. Also, you pre-build the styles, why would the user need the styled components library at all, at that point?
Shameless plug, this is how to do it the right way with all the modern tools.
dev.to/apestein/how-to-publish-to-...
Ayy!! thank you for putting it here. I'll update the article too. :D