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

@gaignoux/frontend-artisan

v0.0.2

Published

Artisan frontend generator base on plop

Downloads

61

Readme

Frontend Artisan / React

Frontend Artisan is a react typescript generator to assist in various projects.

What is this repository for?

  • Quick summary

It is available to support your development by making commands to auto generate api | components | types | interfaces | hooks | context | hoc. Initially the idea was to help new and even more experienced developers to speed up daily development. Removing the need to manually create files that will often have standard structures.

How do I get set up?

  • Summary of set up

First you will need to install the tool in your project of choice, like this:

$    npm i --save-dev @gaignoux/frontend-artisan plop
  • Configuration

Create a plofile.js at the root of your project

module.exports = function (plop) {
	// Here you will load artisan to plop instance
  plop.load('@gaignoux/frontend-artisan');
};

Now you will need to put into your package.json file, a script to run every time you need. Like this:

{
  "scripts": {
    "artisan": "plop --plofile plofile.js"
  }
} 

You can set your own paths as the default setting, so the craftsman doesn't ask you every time he wants to create a new file. For example:

module.exports = function (plop) {
  // Here you will load artisan to plop instance
  plop.load('@gaignoux/frontend-artisan', {
    components: './src/components', // your location for components
    contexts: './src/contexts', // your location for contexts
    hocs: './src/hocs', // your location for hocs
    hooks: './src/hooks', // your location for hooks
    interfaces: './src/interfaces', // your location for interfaces
    types: './src/types', // your location for types
  });
};

Now just test and use as needed.

$    npm run artisan

// or

$    yarn artisan

If you don't want to customize your settings and control the plop command, you can simply call the program directly by configuring it like this:

{
  "scripts": {
    "artisan": "npx @gaignoux/frontend-artisan generate"
  }
} 

And now you can run the previous step that will work in a similar way, but always asking which path you want to create the files.

Test is based on jest, so you just need to contribute and run npm run test;

  • Deployment instructions

No need to implement none of scripts. If you contribute to the project, you only need to run npm run publish:patch to publish a tag like 0.0.1. But if you need to publish a minor or mayor, you just need to run npm run publish:minor or npm run publish:major.

Contribution guidelines

  • Writing tests

Please follow jest test struct. That's the only requirement.

  • Code review

If you found something wrong or witch could be better, fell free to send your pull request for master branch. The package is public but please keep the order.

Who do I talk to?

  • Repo owner or admin

Bruno Gaignoux

  • Other community or team contact

Discord: Bruno Gaignoux#3331