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

@castrolol/samplexxx

v2.1.0

Published

Boilerplate para iniciar seu node module de componente

Downloads

1

Readme

Sample of Component

Aqui você descreve o uso do seu componente

Não se esqueça de informar as dependencias que não veem via npm como jquery, bootstrap, etc.

Exemplo

	<link rel="stylesheet" href="/node_modules/select2/dist/css/select2.css">
	
	<script src="/node_modules/jquery/dist/jquery.min.js"></script>

Aqui ;D

Uso do boilerplate

Não se esqueça de informar as dependencias que não veem via npm como jquery, bootstrap, etc.

Use a parta src para desenvolver o conteudo do seu componente, tentando sempre manter o index.ts como centralizador dos modulos públicos do seu projeto...


	//arquivo index.ts

	export * from './meu-componente.component';
	export * from './outro-componente.component';

	import {MeuComponenteComponent} from './meu-componente.component';
	import {OutroComponenteComponent} from './meu-componente.component';

	//exportar todas as diretivas
	export var MEU_COMPONENT_DIRECTIVES = [
		MeuComponenteComponent,
		OutroComponenteComponent
	];

Comandos

  • Para NPM
    • npm start - Executa junto à um servidor local o sample
    • npm run package - Cria o package distribuivel do seu componente, pronto para ir para o npm
    • npm run publish - Gera o package e tenta atraves de npm publish enviar para o npm.
    • npm run build - Compila o typescript para javascript utilizando o tsconfig.json
  • Para Gulp
    • gulp package - Cria o package distribuivel do seu componente, pronto para ir para o npm
    • gulp publish - Gera o package (via gulp package ) e tenta atraves de npm publish enviar para o npm.
    • gulp serve:sample - Executa junto à um servidor local o sample
    • gulp compile - Compila o typescript para javascript utilizando o tsconfig.json
    • gulp clean - Limpa a pasta de samples e de build
    • gulp assets:copy - Copia o conteudo da pasta de assets (do sample) para a pasta server para desenvolvimento

Sample de testes

O comando para rodar o sample é

	npm start

Estrutura dos Samples

Para alterar o exemplo siga para a pasta sample/src e mude a aplicação angular2 que está lá contida.

Dentro da pasta sample/assets você pode mudar o seu index.html e colocar imagens e coisas assim dentro da task em task/assets.task.js o comportamento é de copiar tudo para server seguindo a hierarquia de pastas presente.