I am making a AngularJS app for a school project. I am using AngularJS, Material, Bower, Bootstrap and Yeoman. Everything was working fine but know my scripts fail to resolve, i resolved a few doing it manually but now i see all the scripts are failing to resolve, making me think there is another issue.
Anyone know what i did :O?
Related
I have an older project that we want to add some more functionality to. It's a fairly big project so rewriting it is out of the question. I've been reading and following the Angular ngUpgrade guide to make the transition to be able to write Angular 2+ code and run it with my AngularJS application.
However, there are some things that I'm missing and I'm quite confused on what I need to do.
My team created the initial project using Grunt and Bower, looks like through a Yeoman generator. I've been following along in the PhoneCat Upgrade Tutorial and I'm at the part where it says to "Install Angular into the project, along with the SystemJS module loader."
At this point I've looked into SystemJS a bit and what we have with our Bower/Grunt setup but am fairly confused.
So my question is, do I need to change my AngularJS application to use SystemJS before continuing with the Angular Upgrade, or can Grunt and SystemJS work together in some way?
I'm looking into creating an app with typescript and angular 1.6.0. But everywhere I look is using webpack, babel, grunt, gulp, there is no single consensus on which is the best way to proceed with an app like this.
Anyone got any hints?
Thank you.
Do you have a specific need for using angular 1.6.0? As opposed to creating an angular2 project?
You can get more information here: Angular-cli
Angular cli currently includes webpack and you will not need to use gulp or grunt at all. In addition to the angular cli bundling your app together it allows easy build for Ahead of Time Compilation and tree shaking. Having these two features is nice for when you are ready to deploy your application to a production server you can bundle the application into a small package and serve a small amount of JS files.
Using the angular cli also helps you to code with best practices within an angular2 application. You generate new components/directives/pipes with a simple ng generate [component] [name] command.
I would strongly suggest reading through the angular quickstart for ts guide located here: Angular-Quickstart
Also, if you do not want to generate your own projects using the angular-cli. There are various templates online that you can start your application with.
Good luck!
If you are planning to start from scratch, then why not Angular2 ?
My suggestion is Typescript2 + Angular2 with webpack. As stated by #Andy Angular-cli is good to go.
i'm developing a website which has a fully Angular front-end.It works well in my local server.When i moved the site to an online one, it gives an bower related error.I was used angular bootstrap ui cdn.But for other Angular related files are loading through a bower.json file.So i'm confused why this error occurs.Hope someone help me to solve this.
I have an Angular App with a significant number of dependencies injected. In development I concatenate the sources (Grunt concat) and the application runs fine.
When I deploy the app I get an error:
http://errors.angularjs.org/1.3.0/$injector/unpr?p0=aProvider%20%3C-%20a
The only significant difference in the build process is that I grunt-ng-annotate and grunt-uglify the sources when I deploy.
I have made a number of module changes since last deploying the app and am finding it difficult to isolate the offending module.
Any suggestions please?
You're probably missing a dependency injection array somewhere, most likely because ng-annotate didn't figure it out. Your best way to debug this (since you're on >= 1.3.0) is to add ng-strict-di to your ng-app, and run it on your ng-annotate'd but not minified source (so tweak your build step). Now Angular will tell you what went wrong. I see from your comment that you tried ng-strict-di but because you used it with your minified source, the error message didn't help you much.
I'm building a app for learning, and I have these major components.
My first question is if these parts are a good foundation for an angularJS app.
I've read in some cases that RequireJS is not a good idea, but not sure why.
My goal is to have a dev environment set up where I have unit and e2e tests, and I want to have this in place before I start coding.
I'm having trouble getting these pieces to work together, and as I push through the issues I thought I'd ask what the latest best practice is to build a non trivial angularJS app.
I have a project that uses AngularJS + RequireJS + Bower + Karma in Github that you can take a look:
http://marcoslin.github.io/angularAMD/
For me, RequireJS has worked very nicely with AngularJS and together it helped tremendously in both application load time and code organisation. I do not use Yeoman yet but Grunt and Bower serve as key foundation for dependency sourcing and building of final project. Karma is a must for unit testing. You should be able see all these components working together in angularAMD Github project.
Your question is a little vague, and answers will be mostly opinions. Anyway, here's mine…
You definitely need node to run all the modern javascript web development tools. (grunt, yeoman, karma, mocha, jshint, uglify, coffee, etc, etc.) Bower is nice to have for updating your client packages. RequireJS is useful for module loading, but not necessary. It should work with AngularJS, but keep in mind that the angular "modules" are completely different from RequireJS "modules". If I were you, I'd work through the Angular tutorial to get a good understanding. Then start your project with yeoman: yo angular.