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

@vmfvmf/jtc

v1.2.133

Published

Schematics to generate a new frontend/backend

Downloads

308

Readme

The argument p2b refers to the files in the folder project-to-build, but it must omit the .js on the arg

After edition on project run 'npm run build' to update de compilation

To create backend, run: schematics .:new-backend --debug=false --prjid=1

To create frontend, run: schematics .:new-frontend --debug=false --prjid=1

To create backend uc run: schematics .:add-backend-artifacts --debug=false --prjid=1

To create frontend component run: schematics .:add-frontend-artifacts --debug=false --ucfid=1

AFTER PUBLISHING: in a project, first execute 'npm init --scope=@vmfvmf' to initialize a npm project then execute 'npm adduser' to add a user from npm finally 'npm publish' to publish to npm

after, published and installed locally, its possible to run:

ng new --collection @vmfvmf/jtc --prjid=1 ng g @vmfvmf/jtc:new-backend --prjid=1 schematics @vmfvmf/jtc:new-backend --prjid=1

TO run specifics add, the project exist in the jtc-output folder.

schematics .:add-frontend-artifacts --ucfid=12 --debug=false

ng generate or g need to be executed inside a angular project, so it cant be executed on a java project

errors: schematics is unknown: npm install -g @angular-devkit/schematics-cli