There is also error caused by webpack-sources

"webpack": "^2.1.0-beta.27"

I got this error after i updated dependencies according to framework updates (http://blog.ionic.io/rc3-error-reporting-final-oh-my/)

[danbucholtz]

Hi @Spaha,

Can you provide some more details or a repo demonstrating the issue?

Thanks,
Dan

[herbzi]

+1
I also had this problem and struggled to find any information on what could be causing it. I had to revert to .46 .

Hi @danbucholtz ,

unfortunately do not have repo for this app. Don't know what exactly from details you need, but after upgrading "@ionic/app-scripts" to latest version (0.0.47) there was also update for webpack, webpack-sources, source-map ( screenshot below)

After that, i try to run "ionic serve" but it resulted with error (screenshot from my previous comment)

(UPDATE) I also tried to create new project with "ionic start cutePuppyPics --v2" and "ionic serve" after setting up project. It doesnt show me error in cmd , but in browsers developer tool it shows that main.js is missing.

Do you need more details ? If yes, be specific please.

Thx,

Haris

[stewones]

ionic-team/ionic-framework#9658 (comment)

[parkbytes]

I was facing the same issue and isolated the problem to multiple components within same .ts file. in my RC3 project.

Update: More specifically this occurs when the second component within the .ts file uses a templateUrl as opposed to template for its decoration.

Applied the single responsibility principle from Angular and separated the components into their respective .ts files to resolve the original issue reported here.

https://angular.io/docs/ts/latest/guide/style-guide.html#!#single-responsibility

I was able to narrow down the issue by manually migrating old rc3 project (part by part) to a freshly created rc4 project.!!!

Maybe the experts can confirm.

[herbzi]

Nice work. I also have multiple components in the same file. Thanks for going through the trouble of isolating it. I think i'll just separate them now considering I had another issue in a previous version of ionic related to this. Might as well stick with the crowd because they don't really test this internally.

Edit: Separating them into individual files worked for me.

[coreymcmahon]

I'm slightly confused by the suggested fix here. It seems to be breaking when there are multiple components within the same .ts file, but that isn't strictly prohibited by Angular 2, right? So this is still a valid bug. Or am I missing something?

[herbzi]

Yes it's still a valid bug that needs addressing. I was just saying that I have had an issue with exactly multiple components within in a single file in the past. #115

This was later fixed and now another issue is cropping up. I'd rather stick with the style guide rather than facing more issues in the future because I don't think they test it internally.

I'm sure someone will come and take a look at it now that we have found a way to reproduce it.

[tkem]

I think I stumbled upon another workaround, which does not require modification of any source files. As documented here, I added the following to my package.json:

 "config": {
 "ionic_source_map_type": "eval"
 }

According to the docs, this will change some webpack option, which defaults to source-map, thus probably triggering the error. Now, I have absolutely no clue what eval does (or webpack in general, for that matter), but for the moment I'm happy enough that I can run ionic serve with app-scripts 0.0.47!

And yes, I (seldomly) do put multiple components in one .ts file; for example, I like to place popups/context menus, which are only a few lines, in the same file as their "parent" page. You may argue about style here, but a build tool still shouldn't croak on this...

[murshid1988]

@tkem This worked for me too. But like you said, this is not a proper fix

[danbucholtz]

@tkem,

I think we'll have some problems indefinitely with multiple components, etc in one file. I don't recommend that right now. We'll fix eventually but bigger fish to fry first.

Thanks,
Dan

[tkem]

@danbucholtz: If that's really been identified as the cause of this issue, that would be fine with me. It's still an RC, after all. I'd just like to see this stated prominently in a list of known bugs/limitations in the release notes.