merjs
Next.js-style web framework in Zig — zero Node.js required.
Installation
pip install merjs
Usage
# Create new project
mer init my-app
cd my-app
# Start dev server
zig build serve
# Build for production
zig build prod
Requirements
- Zig 0.15.1+
- Python 3.8+ (for this installer only)
Platform Support
- macOS (Intel & Apple Silicon)
- Linux (x64 & ARM64)
- Windows (x64)
Documentation
Visit merlionjs.com for full documentation.
License
MIT
Metadata
Release files for merlionjs 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| merlionjs-0.2.2.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| merlionjs-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.1 kB
Release files / merlionjs-0.2.2.tar.gz
| Download URL | merlionjs-0.2.2.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3778492b5c5aaed356464efdedb2044e92b9bd416e07b30e0134c857ed98ca0
|
|
BLAKE2b-256 checksum How to use checksums |
dc8e87a2d136744db577c697232d108b2975c7dd556351ab2b03ba129d615084
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / merlionjs-0.2.2-py3-none-any.whl
| Download URL | merlionjs-0.2.2-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2f550332ba52c843ba2640f9d3d7891ec97b62514c743bd449da63435964291
|
|
BLAKE2b-256 checksum How to use checksums |
f2b01babb2d15488ec811018c4b7e1227ea1fa7645d0a12e69c2659fe950ba65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for merlionjs 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.