@server/next 0.15.0 → 0.15.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@server/next",
-  "version": "0.15.0",
+  "version": "0.15.1",
   "description": "An experimental reimplementation of server.js focused on the DX",
   "homepage": "https://node-server.com/",
   "repository": "https://github.com/franciscop/server-next.git",

package/readme.md

@@ -7,7 +7,7 @@
 A fully-fledged web server for Node.js, with all the basics covered for you:
 
 ```js
-import server, { get, post, put, use, error } from 'server';
+import server, { get, post, put, use } from 'server';
 
 // Create a running instance of the server
 const app = server(config, [pluginA, pluginB]);
@@ -17,8 +17,7 @@ app([
   get('/users', getUsers),
   post('/users', createUser),
   put('/users/:id', editUser),
-  use('/admin/*', dashboard),
-  error(ctx => console.log(ctx.error))
+  use('/admin/*', dashboard)
 ]);
 ```
 
@@ -41,7 +40,9 @@ Why? The ecosystem is moving out of server-rendered websites so we are as well.
 
 ## Progress
 
-- Router has `get` and `post`, as well as URL pattern matches
+- Router has all verbs, as well as URL pattern matches
+- Full URL parsing, including `query` and `params` in ctx.url.
+- Body and Files parsing is working (TODO: try with binary files and add tests)
 - The middleware can return:
   - A number and it'll be set as the status code
   - A string and it'll be sent as plain text or html (if it starts with "<")

package/src/index.js

@@ -278,3 +278,12 @@ export const head = (pattern, callback) => {
     return callback(ctx);
   };
 };
+
+export const use = (pattern, callback) => {
+  return (ctx) => {
+    const match = pathPattern(pattern, ctx.url.path);
+    if (!match) return null;
+    ctx.url.params = match;
+    return callback(ctx);
+  };
+};