htmv 0.0.63 → 0.0.65

package/README.md

@@ -156,9 +156,40 @@ For this, you'll need attribute binding. And HTMV has got your back! Simply add
 
 This tells HTMV's compiler: *"Don't add the attribute AND value, just add the attribute alone IF the value is truthy!"* 
 
+# Components
+One of HTMV's key values is that a component is just a view. Therefore, your `example` view is already a component!
+
+However, for HTMV to be able to differentiate it from an HTML element it must start with an uppercase (`Example`).
+
+Let's create a header component with `bunx htmv gen view Header`
+
+Inside we can make use of attributes like so:
+```html
+<h1>{title}</h1>
+<h2>{description}</h2>
+```
+Lastly, in our `example` view, let's call it!
+```html
+<Header title="My cool webpage" description="It's purpose is to test HTMV's components!"/>
+```
+
+That's it. We can also make use of the `children` prop, like so:
+```html
+<!-- example view -->
+<Header description="It's purpose is to test HTMV's components!">My cool webpage</Header>
+```
+```html
+<!-- Header view -->
+<h1>{children}</h1>
+<h2>{description}</h2>
+```
+
 
 # Hot reloading
-Having to restart the server every time you make a change can be quite tedious. HTMV takes care of this thanks to Bun. Just develop with `bun dev` and it should work out of the box! Note that this does not include hot reloading in the browser. As of now, you have to refresh the page to see new changes. It doesn't update in real time.
+Hot reloading has not yet been fully developed. For now, you may develop with `bun dev`, which will take care of reloading on route code change. However, note that this won't include views or hot reloading in the browser.
+
+# Linting
+As of now, views work under the `.html` extension. However, that is subject to change in the future due to HTMV's language adding features which do not exist on normal HTML. Expect errors to appear on your editor when working with views. This will get sorted out once the `.htmv` extension becomes available.
 
 # Still have questions?
 How about asking the DeepWiki instead?

package/dist/http/helpers.d.ts

@@ -4,3 +4,5 @@ export declare function badRequest(body?: string | object, headers?: Headers): H
 export declare function created(body?: string | object, headers?: Headers): HttpResponse;
 export declare function ok(body?: string | object, headers?: Headers): HttpResponse;
 export declare function noContent(headers?: Headers): HttpResponse;
+export declare function unauthorized(body?: string | object, headers?: Headers): HttpResponse;
+export declare function forbidden(body?: string | object, headers?: Headers): HttpResponse;

package/dist/http/helpers.js

@@ -14,3 +14,9 @@ export function ok(body, headers) {
 export function noContent(headers) {
     return requestHelper(204, undefined, headers);
 }
+export function unauthorized(body, headers) {
+    return requestHelper(401, body, headers);
+}
+export function forbidden(body, headers) {
+    return requestHelper(403, body, headers);
+}

package/dist/views-registry.js

@@ -4,8 +4,6 @@ import { viewsPath } from "./views";
 export const viewRegistry = {};
 export function addToViewRegistry(name, code) {
     viewRegistry[name] = code;
-    console.log("Registered view", name, "with code:");
-    console.log(code);
 }
 export async function registerViews() {
     const files = await deepReadDir(viewsPath);

package/package.json

@@ -2,7 +2,7 @@
 	"name": "htmv",
 	"main": "dist/index.js",
 	"type": "module",
-	"version": "0.0.63",
+	"version": "0.0.65",
 	"exports": {
 		".": {
 			"types": "./dist/index.d.ts",