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

railinc-angular-seed

v1.0.1

Published

Railinc Angular Seed Project: (Router, Http, Forms, Services, Tests, E2E, Coverage), Karma, Protractor, Jasmine, TypeScript

Downloads

5

Readme

Railinc Angular Seed Project

The Official Railinc Angular 4 Seed Project.

Clone this repo and follow the steps below to get started with Angular 4 Web Application Development.

Getting Started

Assumptions / Prerequisites:

  • Angular 4 Development absolutely requires that the developer is developing on a VM

  • Please use the following Vagrant project if you don't already use a preferred setup: http://gitgogs.railinc.com:3000/railinc-developer/railinc-dev-workstation

  • If you are using a different VM setup, the following items are recommended:

    • Using Visual Studio Code as your IDE
    • Installing NVM to manage your NodeJs versions
    • Using NodeJs 6.11.3 LTS

Setup Steps:

  • Until this project is integrated into the Railinc Application Archetype, you must first clone this repo in the UI-Build module of the archetype. Remove all previously existing files. This repo does include a pom.xml file, which is based on Commercial RailSight projects. You'll need to modify it to fit your project.
> git clone  http://gitgogs.railinc.com:3000/railinc-ui/railinc-angular-seed.git

Modify the output directory:

By default, the output directory is setup to create a target folder in the UI-Build maven module, however, this setup is specific to Commercial Railsight projects. If this is not a commercial project, you'll need to change this to put the final bundled assets into the integration module when the UI-Build module is run. To do this you'll need to modify the webpack.prod.js file, found at:

web/
 ├──config/                        * our configuration
 |   ├──webpack.prod.js                 * Production Webpack Configuration File
  • Change this line:
      path: helpers.root('..', 'target', 'classes', 'META-INF', 'resources' )
  • to:
      path: helpers.root('..', '..', 'integration', 'src', 'main', 'webapp' )
  • Please note that "integration" is referring to whatever the folder name is of your integration module. It may not be "integration".

Download Project Dependencies:

  • Open Visual Studio Code and open the "web" folder of the cloned project:

    • File > Open Folder... > Select the "web" folder of your project
  • Open the built-in Terminal in Visual Studio Code:

    • [CTRL + ~]
  • Run the initial install of the required node modules, defined in the package.json file. This may take a couple minutes

> npm i

Starting the Application:

  • Now that all the dependencies have been downloaded and live in the "node_modules" directory, the application can be started.
> npm start
  • This will start the web application, which can be accessed at http://localhost:3000

Things to ignore (not commit):

  • node_modules/
  • compiled/
  • dll/