| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
# clone the repo
git clone git@github.com:meenie/angular2-store-example.git
# change directory to our repo
cd angular2-store-example
# install the repo with npm
npm install
# start the server
npm startgo to http://0.0.0.0:3000 in your browser
We use the component approach in our starter. This is the new standard for developing Angular apps and a great way to ensure maintainable code by encapsulation of our behavior logic. A component is basically a self contained app usually in a single file or a folder with each concern as a file: style, template, specs, e2e, and component class. Here's how it looks:
angular2-webpack-starter/ ├──src/ * our source files that will be compiled to javascript | ├──main.ts * our entry file for our browser environment │ │ | ├──index.html * Index.html: where we generate our index page │ │ | ├──vendor.ts * our vendor file │ │ │ ├──app/ * WebApp: folder │ │ ├──app.spec.ts * a simple test of components in app.ts │ │ └──app.ts * App.ts: a simple version of our App component components │ │ │ └──assets/ * static assets are served here │ ├──icon/ * our list of icons from www.favicon-generator.org │ ├──service-worker.js * ignore this. Web App service worker that's not complete yet │ ├──robots.txt * for search engines to crawl your website │ └──human.txt * for humans to know who the developers are │ ├──test/ * this is our global unit tests and end-to-end tests │ ├──spec-bundle.js * ignore this magic that sets up our angular 2 testing environment ├──karma.config.js * karma config for our unit tests ├──protractor.config.js * protractor config for our end-to-end tests │ ├──tsconfig.json * config that webpack uses for typescript ├──typings.json * our typings manager ├──package.json * what npm uses to manage it's dependencies │ ├──webpack.config.js * our development webpack config ├──webpack.test.config.js * our testing webpack config └──webpack.prod.config.js * our production webpack config
This project uses json-server as an API to help with CRUD operations on the front-end. Please read the documentation in the provided link to learn more on how you can use it. After running npm install, there is a postinstall script which will generate the file called db.json with some seeded data. Change this all you like, it has been .gitignored.
What you need to run this app:
Once you have those, you should install these globals with npm install --global:
After you have installed all dependencies you can now run the app. Run npm start to start a local server using webpack-dev-server which will watch, build (in-memory), and reload for you. The port will be displayed to you as http://0.0.0.0:3000.
There are a couple of environment variables you can set to change some of the server settings:
# development
npm start
# production
npm run build:prod
npm run server:prod# development
npm run build:dev
# production
npm run build:prodnpm run watchnpm run testnpm run webdriver:update
npm run webdriver:start# make sure you have webdriver running and a sever for the client app
npm run e2ePlease do :).
To take full advantage of TypeScript with autocomplete you would have to install it globally and use an editor with the correct TypeScript plugins.
TypeScript 1.7.x includes everything you need. Make sure to upgrade, even if you installed TypeScript previously.
npm install --global typescript
We have good experience using these editors:
| Back | FazBrowse Home | New Git URL |