npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@trapcode/xpresser-frontend-helpers

v1.1.12

Published

Xpresser Frontend Helper

Downloads

8

Readme

XpresserJs Frontend Helpers

Create a javascript file of all named routes that can be imported and bundled by webpack.

Problem

When working with lots of routes, Sometimes you find it difficult to remember the url of your routes And the glorious xpresser $.helpers.route() helper function that converts names to urls can't be accessed in Frontend.

For Example, we have a route like this Backend

$.router.get('/user/:userId/uploads/:fileId/') // /user/164/song/733

In our Frontend

axios.get(`/user/${userId}/uploads/${fileId}`)

Remembering urls, required/un-required route named parameters when you have over 500 routes will be difficult.

Solution

AUTOGENERATED routes file that can be imported into your Frontend. This plugin reads your routes then generates a file that can be configured to use any Http Library you are using. This file includes all your routes as a Library.

For example using the same example above, But we have to add a name to identify the route.

router.get('/user/:userId/uploads/:fileId/', http => {
  return {file: 'image.png'}
}).name('uploaded_file') // /user/164/song/733

In your frontend

import req from "./auto-generated-file";

await req.get.uploaded_file([userId, fileId]); // returns {"file": "image.png"}

More Examples

Backend

router.get('/users', 'UserController@users').name('users');
router.post('/users', 'UserController@create').name('user.create');

router.get('/user/:userId', 'UserController@user').name('user');
router.patch('/user/:userId', 'UserController@update').name('user.update');
router.delete('/user/:userId', 'UserController@delete').name('user.delete');

router.get('/songs/:genre/:year?/:month?/:day?').name('songs');

Frontend.

import req from "./auto-generated-file";

await req.get.users({page: 2}) // GET: /user?page=2
await req.post.users({
  id: 35, name: "John Doe", email: "[email protected]", password: "password"
}) // POST: /users with body

await req.get.user(35) // GET: /user/35
await req.patch.user(35, {
  password: "newPassword"
}) // PATCH: /user/35
await req.delete.user(35) // DELETE: /user/35

await req.get.songs(["hip-hop", 2020, 4, 15]) // GET: /songs/hip-hop/2020/4/15

What you get.

  • Autocomplete for faster development.
  • It will never make a Http Verb mistake like send get instead of post.
  • Easily supports any http library.

This came like an idea to me, so I decided to bring it to life.

Note: this is still experimental, I have lots of work on my table. So I won't be paying attention to it for now... I will be updating my local version during my day-to-day use then someday I will update this.

For now, it only generates the file. you have to configure it to work like the Examples above. 🤦‍♂️

You can run the test file included.