With the latest CLI, inside angular.json “test”: { “builder”: “@angular-devkit/build-angular:karma”, “options”: { “main”: “src/test.ts”, “polyfills”: “src/polyfills.ts”, “tsConfig”: “src/tsconfig.spec.json”, “karmaConfig”: “./karma.conf.js”, “codeCoverageExclude”: [“src/testing/**/*”],
The ng g component plainsight/some-name makes a new directory when we use it. The final output will be: plainsight/some-name/some-name.component.ts To avoid that, make use of the flat option ng g component plainsight/some-name –flat and it will generate the files without making a new folder plainsight/some-name.component.ts
What you can do it host the config file in json format in the assets folder and retrieve it dynamically. You need to make sure that you retrieve it before the app starts, that way it can be available in components/services when they need it. For that, you can use the APP_INITIALIZER Token Step #1: … Read more
All static asset files/directories need to be listed in the angular-cli.json file. Adding assets To add your assets you can either: Put your image file in the default assets folder (which is already listed in the angular-cli.json file. Or add a new directory inside of app/ (e.g. in your case you could use app/images, and … Read more
Looks like you forgot to return value from factory: export function init(config: ConfigService) { return () => { return config.load(); // add return }; } or the same code can be written a bit shortly: export function init(config: ConfigService) { return () => config.load(); }
According to the current angular-cli readme (v1.0.1): You use the assets array in angular-cli.json to list files or folders you want to copy as-is when building your project: “assets”: [ “assets”, “favicon.ico” ] By default the assets folder is configured for this, so you can place your files into a structure like ├── src . … Read more
I had the same issue. Created a new project. Built a production version “build-production”: “ng build –configuration=production –extract-css=false –prod –aot” Deployed to NGINX White page with no content between tags in Chrome Element inspector Fix Update tsconfig.json “target”: “es5”, Then rebuild the application and deploy again. This solution worked for me, I now have content … Read more
You simply copy the package and all dependencies in your node_modules folder, inside the project for local installation, or in the global folder (npm config get prefix to see where it is located) for a global installation. The behavior of npm install is to check for the dependencies, and install them first. When it doesn’t … Read more
This is most likely the result of a 404 page or a redirect to a page that serves regular html instead of the expected JavaScript files. (A HTML page starts with <html> or a <!DOCTYPE…>) Make sure that you have correctly uploaded the files and access the page correctly. You can verify by manually accessing … Read more
Make a png image with same name (favicon.png) and change the name in these files: index.html: <link rel=”icon” type=”image/x-icon” href=”https://stackoverflow.com/questions/40817280/favicon.png” /> angular-cli.json: “assets”: [ “assets”, “https://stackoverflow.com/questions/40817280/favicon.png” ], And you will never see the angular default icon again. Size should be 32×32, if more than this it will not display. NOTE: This will not work with … Read more