angular-fullstack
v4.2.0 `npm start` fonts not loading. Is `node server` enough?
- [x ] I understand that GitHub issues are not for tech support, but for questions specific to this generator, bug reports, and feature requests.
| Item | Version |
|---|---|
| generator-angular-fullstack | 4.2.0 |
| Node | 6.10 |
| npm | default |
| Operating System | OS X 10 / Windows 10 / Ubuntu 15.10 / etc |
| Ubuntu 16.04 |
| Item | Answer |
|---|---|
| Transpiler | Babel |
| Markup | HTML |
| SCSS | |
| ui-router | |
| MongoDB | |
| Auth | Y |
| etc |
I just used this to setup a new app.
npm install npm start visit http://localhost:3000/signup look in the inspector and /assets/fonts/* is 404 repo/client/assets/fonts doesn't exist (not sure if that's relevant - just gettign started)
Several bugs related to this were closed in favor of this one. The fix from that has been applied, but I'm still seeing the issue:
GET /assets/fonts/font-awesome/fontawesome-webfont.woff2?v=4.7.0 404 3.940 ms - -
I tried the fix mentioned here but it didn't work.
npm start is node server. Should that maybe be gulp serve? It seems gulp serve is doing a bit more. Or needs npm build to be run first. Maybe it's something or the README next to gulp build
Thanks!
Mike
I believe the idea is that npm start is for a built app, most likely in a production setting. We probably need better doc on this.
