create-react-app-zero
iceberg
Our great sponsors
| create-react-app-zero | iceberg | |
|---|---|---|
| 7 | 1 | |
| 26 | 0 | |
| - | - | |
| 0.0 | 10.0 | |
| over 1 year ago | over 1 year ago | |
| JavaScript | Python | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
create-react-app-zero
-
Writing JavaScript without a build system
https://github.com/jsebrech/create-react-app-zero
-
Why is the JavaScript ecosystem like this
No build frontend dev is a thing, although obscure.
Preact has a no build path in their documentation: https://preactjs.com/guide/v10/getting-started/#no-build-too...
And here’s my no build react setup: https://github.com/jsebrech/create-react-app-zero
-
Ask HN: Programming Without a Build System?
Not really the thing you’re looking for, but for those looking for a toolless approach static web apps are a possibility. Host a folder on github pages, put an index.html file in there, start coding.
Plugging my own repo: https://github.com/jsebrech/create-react-app-zero
It is a version of create react app that works in that way, no build tools needed, only a static web server for local development.
-
What unpopular webdev opinions do you have?
For example, I made a version of create react app that requires zero build tools and IMHO doesn't concede too much in developer experience. To be fair, I am not using this myself professionally, but as a proof of concept I think it's pretty interesting to see what's possible. https://github.com/jsebrech/create-react-app-zero
- JS is USELESS without ... [fill in the blank]
-
Is the madness ever going to end?
I have been in professional web development since 2004 and I mostly agree with the author that there are massive amounts of groupthink going on. "Modern" web development has standardized in tool stacks which are insanely complicated, far beyond anything that is warranted in most cases. We have forgotten how to make simple things in simple ways.
At a minimum you need node, npm, webpack, babel, an spa framework, a frontend router, a css transpiler, a css framework, a test runner, a testing functions library, and a bunch of smaller things, and that's just what is "needed" to build a static website with a bit of interaction. We're not even talking about the dockerized insanity that happens as soon as you want to slide an API under that beast.
I understand why every piece is there, I was there when they arrived on the scene, I understand what problem they solve. What I don't understand is why as a group web developers have decided this is the only way to solve the problem of web development. What we don't have are simpler web stacks. Why do we need npm or babel at all to make a simple web frontend? Modern browsers are good enough that with the right tooling we don't need build pipelines or package managers. Similar arguments can be made for the server-side parts.
Anyway, here's my own two cents to a simpler web dev stack: a version of create react app that is entirely self-contained and has no build steps. https://github.com/jsebrech/create-react-app-zero
- Show HN: Create React App Zero, a no build tools way of making a React app
iceberg
-
Ask HN: Programming Without a Build System?
Details I didn't include but should have (I wasn't sure I'd have any replies at all... I should have had more faith, sorry)
It's a bit of a ramble, sorry about that.
MSTOICAL[0] is a fork of an old C based Forth variant, it took some help from the HN community[1] to get it to compile in a modern 64 bit environment, for which I am very thankful. However, it uses AutoConf to configure, build, install, etc... and I can't for the life of me figure out how to remove all of that logic. (C isn't my primary language, I'm willing to learn that, but adding AutoConf on top of it was too much)
In order to work on that, I was willing to switch to Linux (Ubuntu)... got everything up and running for the most part, but then I couldn't access WikidPad[2], my local Wiki with my appointments, etc. I missed a doctors appointment because of that, so went back to Windows.
The issue is around wxWindows changing the names of variables in some calls. On Windows, you just download an EXE installer and you're good to go. I couldn't figure it out because the program seems to be unwilling to support newer Python versions. (I could be wrong)
I don't understand why they felt the need to make breaking changes to wxWindows, and the python is a bit too dense for me.
So finally... I'm back in Windows 10, and decided to try to craft together a twitter clone with a bunch of weird ideas that I tossed out at 3:30 am in a twitter thread, and put into a more coherent manifesto.[3]
[0] https://github.com/mikewarot/mstoical
[1] https://news.ycombinator.com/item?id=30957273
[2] https://github.com/WikidPad/WikidPad
[3] https://github.com/mikewarot/iceberg/blob/main/MANIFESTO.md
What are some alternatives?
Telegram-web-z - Telegram Web Z, GPL v3
mu1 - Prototype tree-walking interpreter back when Mu was a high-level statement-oriented language, c. 2018
unik - The Unikernel & MicroVM Compilation and Deployment Platform
llvm-mingw - An LLVM/Clang/LLD based mingw-w64 toolchain
mstoical - MStoical - a Forth like language, but better
pyenv-virtualenv - a pyenv plugin to manage virtualenv (a.k.a. python-virtualenv)
htmx - </> htmx - high power tools for HTML
Odin - Odin Programming Language
Visual Studio Code - Visual Studio Code
Poetry - Python packaging and dependency management made easy