1.0.0-beta.16 broke the "assets" functionality

[vkniazeu]

1. Windows 10 Pro 64-bit.
2. angular-cli: 1.0.0-beta.16
   node: 6.7.0
   os: win32 x64
3. Updated from 1.0.0-beta.15 to 1.0.0-beta.16.
   Same exact "assets" directory and related config files setup worked fine before.
4. ERROR in ./src/app/login/login.component.html
   Module not found: Error: Can't resolve './assets/logo.png' in 'C:\project1\src\app\login'
   @ ./src/app/login/login.component.html 1:92-120
   @ ./src/app/login/login.component.ts
   @ ./src/app/login/index.ts
   @ ./src/app/app.module.ts
   @ ./src/app/index.ts
   @ ./src/main.ts
   @ multi main
5. Are there any new restrictions on what assets can be used and how they need to be configured?
   The CHANGELOG doesn't seem to indicate anything that would be related to the assets.
   Could fix(build): use config output path as default #2158 have potentially affected this flow?

[thephred]

I made the comment in the gitter room. Please disregard, it was a red herring.

[ellipizle]

same problem here too

[monojack]

Was able to fix that by adding a / în front of assets. So, assets/logo.png should be /assets/logo.png.

[ellipizle]

yes. that solve the issue

[jfmaeck]

OK, that sounds like a workaround for most cases, thank you @monojack .

Has anybody any idea how to overcome this issue if my app is not not served directly from the root of my domain (but from a subdirectory)?

By the way, this problem creeped into beta.15, too. Our project was building just fine but on a fresh checkout and npm install, since today it is broken ...

[Bulan]

Same here, working on beta 15, now either have to use / in path or make the relative path point up to src by using appropriate number of ../.
I.e in my src/app/shared/layout/header/header.html, I have to use../../../../assets/someimg.jpg

[clydin]

It looks like the use of the html-loader was added via the AOT support PR. (commit: d296778)
html-loader attempts to find the assets at build time and assumes the assets are relative to the referencing HTML file.

@hansl

[davinkevin]

The solution of @monojack doesn't work if you publish with a different <base></base> (with ng github-pages:deploy for example). This lead to broken assets

[MuhammedHasan]

As @davinkevin mention, it do not work with custom base tag.

[filipesilva]

@TheLarkInn is there a way to use https://github.com/webpack/html-loader in which it works with relative paths AND with changed base-href?

Edit: some context webpack-contrib/html-loader#85