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

starter-kit-angular

v1.3.0

Published

Starter Kit for Angular v1

Downloads

4

Readme

starter-kit-angular

Starter Kit for Angular v1.

Usage:

Just use this kit as base code to start your Angular project

  • Entry page source: /src/index.html
  • All source files will be bundled into /app/
  • Use Webpack 2 to bundle files
  • Use LESS for CSS pre-process, but you can choose on your own such as SASS.

bundle all files

npm run dist

start webpack dev server

npm run dev

You can also use the following command to bundle all files and then start dev server.

npm start

Structure

starter-kit-angular/
 ├──app/                           * all bundles
 │
 ├──src/                           * source files that will be all bundled to /app/dist/
 |   ├──index.html                 * app entry page source file
 │   │
 |   ├──critical.js                * critical process, such as page loading styles
 |   ├──critical.less              * critical styles
 │   │
 |   ├──main.js
 |   ├──main.less
 │   │
 │   ├──_core/                     * core Javascript files
 │   │   └──routers.less           * Angular router configurations
 │   │
 │   ├──_core-less/                * core Less files
 │   │   ├──_include.less          * include all base Less files, you can include this file in all your Less files
 │   │   ├──color.less             * color configurations
 │   │   ├──tools.less             * base mixins
 │   │   └──variables.less         * other configurations
 │   │
 │   ├──_webpack/                  * webpack configuration
 │   │   ├──_base.js
 │   │   ├──dev.js                 * will use this config for development environment
 │   │   └──dist.js                * will use this config for production environment
 │   │
 │   ├──templates/                 * templates used for router
 │   │   └──${template}.js
 │   │
 │   ├──controllers/
 │   │   └──${controller}.js
 │   │
 │   ├──components/
 │   │   └──${component}.js
 │   │
 │   └──services/
 │       └──${service}.js
 │
 └──webpack.config.js              * webpack main configuration file

Services and Controllers

You will noticed that there're services, controllers and components folder under src. These are used for my strategy for bundling services, controllers and components.

  1. Services and Controllers names are defined in src/main.js in array services and controllers.
  2. The process will find src/services/${serviceName} for the service by that name, src/controllers/${controllerName} for the controller by that name and src/components/${componentName} for the component by that name and then bundle them.

License

MIT