Fast learning, preprocessing, intuitive web framework.
Rino.js is created to fix the complexity matters of web framework.
The recommended way to start your Rino project:
npm create rino@latest
For manual setup:
npm i rinojs
Rino.js is going to be version 3.0.0 after some of new features and bugs are sorted. I know my versioning style is not that great. But I want Rino.js version 3 to be more completed than beginning of version 2.
Cleared outdated packages and checked bugs. Which caused some changes. Please report any problem.
@Now from version 2.19.0 we need to rino- instead of @ for attributes.
<component rino-path="/common/head" />
<component rino-path="/common/header" rino-tag="header"></component>
<script rino-type="markdown" rino-path="/docs/getting-started.md"></script>
Input:
\<lang>head.title\</lang>
<p><lang>head.title</lang></p>
<p><lang>missing.value</lang></p>
Output:
<lang>head.title</lang>
<p>Translated Title Here</p>
<p><lang>missing.value</lang></p>
Now i18n pages are going to be included in project sitemap generation.
Rino.js now has a fully-featured, flexible, and developer-friendly JSON-based internationalization system for both dev server and static generation. Localization is now deeply integrated into the compiler pipeline while staying simple and intuitive to use.
pages/
index.html
about.html
i18n/
en/
index.json
about.json
ko/
index.json
about.json
Each <lang>...</lang> tag in your HTML will map to a key inside the corresponding JSON file:
<h1><lang>header.title</lang></h1>
<p><lang>body.content.top[0]</lang></p>
{
"header": { "title": "Welcome" },
"body": {
"content": { "top": ["First content block"] }
}
}
You can explicitly define which locales should be built and served.
Only "en" and "ko" directories under /i18n/ are used.
All other locale folders are ignored (safe, predictable output).
defaultLocale is applied to root pages (e.g. /index.html).
Localized pages will be generated under /dist/<locale>/ automatically.
i18n: {
defaultLocale: "en",
locales: ["en", "ko"]
}
New version, better development experience and totally different from version 1.
Many syntax is simplified and following html, css and javascript standard. And many things are updated for automation.
Development Build System is changed to the server side rendering with memory data management with individual IO update on change. I call this, build on request. This is so much faster than version 1.
<!DOCTYPE html>
<html>
<head></head>
<body>
<component
@path="button"
@tag="button"
type="button"
onclick="alert('Hello world!')"
/>
<component @path="footer" @tag="footer" />
<script @type="md" style="color: red" type="text/markdown">
## test
test
- test
</script>
<script @type="ts" type="text/typescript">
// This is for templating html content
let world: string = "Hello world! from typescript";
console.log(world);
</script>
<script @type="js" type="text/javascript">
// This is for templating html content
console.log("Hello world! from javascript");
</script>
</body>
</html>
Right now end to end testing is implemented for test backoffice website with cypresss and playright. Both can be used to test backoffice website by:
npm run test-cp
Which is npx cypress open
npm run test-pw
Which is npx playwright test
I am thinking of using jest.
MIT, See LICENSE.
FAQs
Fast learning, preprocessing, intuitive web framework
The npm package rinojs receives a total of 66 weekly downloads. As such, rinojs popularity was classified as not popular.
We found that rinojs demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.
Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.