Error aSource is not in the SourceMap #1982

chosroes · 2016-09-05T11:14:07Z

Please provide us with the following information:

OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Ubuntu 16.04
Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:
angular-cli: local (v1.0.0-beta.11-webpack.8, branch: master)
node: 6.5.0
os: linux x64
Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
I updated to master branch and tried to build or serve
The log given by the failure. Normally this include a stack trace and some
more information.

/home/test/angular-cli/node_modules/webpack-sources/node_modules/source-map/lib/source-map-consumer.js:704
      throw new Error('"' + aSource + '" is not in the SourceMap.');
            ^
Error: "/home/test/angular-cli/node_modules/angular2-template-loader/index.js!/var/www/html/public/project/src/app/app.component.ts" is not in the SourceMap.
    at SourceMapConsumer_sourceContentFor [as sourceContentFor] (/home/test/angular-cli/node_modules/webpack-sources/node_modules/source-map/lib/source-map-consumer.js:704:13)
    at /home/test/angular-cli/node_modules/webpack-sources/node_modules/source-map/lib/source-node.js:133:40
    at Array.forEach (native)
    at Function.SourceNode_fromStringWithSourceMap [as fromStringWithSourceMap] (/home/test/angular-cli/node_modules/webpack-sources/node_modules/source-map/lib/source-node.js:132:32)
    at SourceMapSource.node (/home/test/angular-cli/node_modules/webpack-sources/lib/SourceMapSource.js:42:20)
    at ReplaceSource.node (/home/test/angular-cli/node_modules/webpack-sources/lib/ReplaceSource.js:66:29)
    at CachedSource.node (/home/test/angular-cli/node_modules/webpack-sources/lib/CachedSource.js:12:23)
    at /home/test/angular-cli/node_modules/webpack-sources/lib/ConcatSource.js:40:49
    at Array.map (native)
    at ConcatSource.node (/home/test/angular-cli/node_modules/webpack-sources/lib/ConcatSource.js:39:60)
    at /home/test/angular-cli/node_modules/webpack-sources/lib/ConcatSource.js:40:49
    at Array.map (native)
    at ConcatSource.node (/home/test/angular-cli/node_modules/webpack-sources/lib/ConcatSource.js:39:60)
    at /home/test/angular-cli/node_modules/webpack-sources/lib/ConcatSource.js:40:49
    at Array.map (native)
    at ConcatSource.node (/home/test/angular-cli/node_modules/webpack-sources/lib/ConcatSource.js:39:60)
    at /home/test/angular-cli/node_modules/webpack-sources/lib/ConcatSource.js:40:49
    at Array.map (native)
    at ConcatSource.node (/home/test/angular-cli/node_modules/webpack-sources/lib/ConcatSource.js:39:60)
    at ConcatSource.proto.sourceAndMap (/home/test/angular-cli/node_modules/webpack-sources/lib/SourceAndMapMixin.js:28:18)
    at CachedSource.sourceAndMap (/home/test/angular-cli/node_modules/webpack-sources/lib/CachedSource.js:51:28)
    at Compilation.<anonymous> (/home/test/angular-cli/node_modules/webpack/lib/SourceMapDevToolPlugin.js:57:32)

Mention any other details that might be useful.

The text was updated successfully, but these errors were encountered:

chosroes · 2016-09-05T12:28:26Z

~~When I set a new project with ng new foo --link-cli, the problem doesn't occur.~~
~~I have done npm link angular-cli on the old one.~~

It doesn't work under /var/www/html/public but it does under /home/myuser
Is it because angular-cli is cloned under my user folder ?

It works when i copy the cloned folder under my project node_modules folder

Chabane · 2016-09-05T20:39:56Z

I have the same issue on Mac OS X Yosemite.

rokde · 2016-09-15T06:49:29Z

The same on:

angular-cli: 1.0.0-beta.14
node: 6.4.0
os: linux x64

divid3byzero · 2016-09-20T15:46:42Z

I have the same issue with if angular-cli is installed globally:

angular-cli: 1.0.0-beta.15
node: 6.4.0
os: darwin x64 (El Capitan 10.11.6)

Works if the CLI ist installed locally. Possibly some rights issue? Even though the error would then probably be somehow different...

joao-fidalgo · 2016-09-20T16:03:35Z

Having the same issue.

Djuki · 2016-09-25T10:08:58Z

Same issue:

angular-cli: 1.0.0-beta.15
node: 6.6.0
os: linux x64

MartinNuc · 2016-09-25T11:00:08Z

Same issue.

angular-cli: 1.0.0-beta.15
node: 6.6.0
os: darwin x64

ghost · 2016-09-25T19:20:40Z

Same on Mac os El Capitan:

angular-cli: 1.0.0-beta.15
node: 6.6.0
os: darwin x64

brianmadden · 2016-09-27T03:09:00Z

Same issue.
angular-cli: 1.0.0-beta.15
node: 4.2.6
os: Ubuntu 16.04 x64

Additional details: Created the project on my laptop (also Ubuntu 16.04, angular-cli 1.0.0-beta.15, node 4.2.6) and it built/served fine. This failure occurs on my desktop after git cloneing the repo.

Edit: Ran a git clean -dfx followed by npm install followed by ng serve and it seems to be working now. I'm guessing there was some leftover stuff in the directory from prior to migrating my project to use angular-cli.

CalebMacdonaldBlack · 2016-10-03T01:02:40Z

@brianmadden Thank you so much! this worked for me

ewu-youngb · 2016-10-03T17:41:08Z

@brianmadden Thanks, that helped!

svensp · 2016-10-05T16:16:59Z

For us this happens when we give the node_modules as symlink instead of a folder inside the source. Presumably the webpack tries to include node_modules/.. into the sourcemap.
Since it is a symlink app/node_modules/.. is not actualy the same as app/ so the app directory is not included in the sourcemap.

filipesilva · 2016-10-09T19:04:39Z

I'm having some trouble understanding this issue. So this happens when using the master branch directly, right? What else are you doing? Can you give me very explicit instructions for me to repro it?

I use the master branch every day and haven't ever seen this happen, so I'm wondering what the setup is, and how it differs from mine.

brianmadden · 2016-10-10T02:01:19Z

I think my case was caused by re-using an existing directory for my project. When I initially set the project up I re-used my existing project directory. Prior to initializing the cli project I did a rm -rf * in the project directory and everything worked on that computer.

I then pushed to github and pulled on my laptop. This is where I believe things went wrong. There were files left over on my laptop from the old project, but they weren't tracked by git so weren't deleted when I pulled. I think the problem was the lingering files, and this is why the git clean and re-run of npm install fixed the issue for me.

rokde · 2016-10-10T06:13:47Z

@svensp said, that we are using a symlinked "node_modules" folder. And running the build process does not handle the correct resolvement of the "../node_modules" (in webpack) to get the correct real path.

This happens in our docker node environment where the node_modules folder is just a symlink from within the docker image/container. So your project dir has not the node_modules content, only the symlink.

filipesilva · 2016-10-10T15:33:36Z

This might solve it then #2291. Can you test making this change manually?

chosroes · 2016-10-13T12:23:30Z

I updated to latest angular-cli (no master anymore).
What I've done:
sudo npm uninstall -g angular-cli
sudo npm cache clean
sudo npm install -g angular-cli@latest
rm -rf node_modules dist tmp
npm link angular-cli
ng init

Then ng serve. And I still have the error.

I do not have angular-cli/models/webpack-build-common.ts file in my node_modules.

My project was initiated on beta.11-webpack.8 version. And I updated regularly the code.

filipesilva · 2016-10-14T16:16:22Z

Fixed by #2291

vinchauhan · 2016-10-18T23:19:07Z

Same issue

vinchauhan · 2016-10-19T08:06:09Z

For some of us the command - ng new app-name - needs to be run with sudo

derailed · 2016-11-03T17:07:13Z

Having the exact same issue building a docker image. Using Node:6.7.0 and CLI:1.0.0-beta.19-3. It works fine in dev mode but when I change NODE_ENV=production, $ ng build, fails with the following error:

/usr/lib/node_modules/angular-cli/node_modules/webpack-sources/node_modules/source-map/lib/source-map-consumer.js:704
throw new Error('"' + aSource + '" is not in the SourceMap.');

doliver3 · 2016-11-23T03:09:03Z

I have the same problem on linux with a brand new folder and use of ng init and latest version of node 7. This issue is not fixed.

mayakwd · 2016-12-12T22:48:15Z

Any workaround? Same issue

JSMike · 2017-01-12T15:06:14Z

For docker users. Are your node_modules being shared from the host machine? there may be an issue with how docker follows the sym-links in your mounted directories. Look into installing node_modules with --no-bin-links

valterbarros · 2017-02-01T15:18:16Z

@JSMike how can install with --no-bin-links, it's a flag in ng? Thank you

JSMike · 2017-02-02T15:03:58Z

it's an NPM flag, you can do ng new ProjectName --skip-npm and then npm install --no-bin-links

valterbarros · 2017-02-02T18:32:01Z

@JSMike Thank it's work here

angular-automatic-lock-bot · 2019-09-06T16:41:16Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

filipesilva added the needs: more info Reporter must clarify the issue label Oct 9, 2016

filipesilva mentioned this issue Oct 14, 2016

ng serve error localhost could NOT be bound #2587

Closed

filipesilva closed this as completed Oct 14, 2016

johnlindquist mentioned this issue Mar 22, 2017

Errors out with SourceMaps Error KidkArolis/jetpack#6

Closed

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error aSource is not in the SourceMap #1982

Error aSource is not in the SourceMap #1982

chosroes commented Sep 5, 2016 •

edited

Loading

Please provide us with the following information:

chosroes commented Sep 5, 2016 •

edited

Loading

Chabane commented Sep 5, 2016

rokde commented Sep 15, 2016

divid3byzero commented Sep 20, 2016 •

edited

Loading

joao-fidalgo commented Sep 20, 2016

Djuki commented Sep 25, 2016

MartinNuc commented Sep 25, 2016 •

edited

Loading

ghost commented Sep 25, 2016

brianmadden commented Sep 27, 2016 •

edited

Loading

CalebMacdonaldBlack commented Oct 3, 2016

ewu-youngb commented Oct 3, 2016

svensp commented Oct 5, 2016

filipesilva commented Oct 9, 2016

brianmadden commented Oct 10, 2016

rokde commented Oct 10, 2016

filipesilva commented Oct 10, 2016 •

edited

Loading

chosroes commented Oct 13, 2016

filipesilva commented Oct 14, 2016

vinchauhan commented Oct 18, 2016

vinchauhan commented Oct 19, 2016

derailed commented Nov 3, 2016

doliver3 commented Nov 23, 2016

mayakwd commented Dec 12, 2016

JSMike commented Jan 12, 2017

valterbarros commented Feb 1, 2017

JSMike commented Feb 2, 2017 •

edited

Loading

valterbarros commented Feb 2, 2017

angular-automatic-lock-bot bot commented Sep 6, 2019

Error aSource is not in the SourceMap #1982

Error aSource is not in the SourceMap #1982

Comments

chosroes commented Sep 5, 2016 • edited Loading

Please provide us with the following information:

chosroes commented Sep 5, 2016 • edited Loading

Chabane commented Sep 5, 2016

rokde commented Sep 15, 2016

divid3byzero commented Sep 20, 2016 • edited Loading

joao-fidalgo commented Sep 20, 2016

Djuki commented Sep 25, 2016

MartinNuc commented Sep 25, 2016 • edited Loading

ghost commented Sep 25, 2016

brianmadden commented Sep 27, 2016 • edited Loading

CalebMacdonaldBlack commented Oct 3, 2016

ewu-youngb commented Oct 3, 2016

svensp commented Oct 5, 2016

filipesilva commented Oct 9, 2016

brianmadden commented Oct 10, 2016

rokde commented Oct 10, 2016

filipesilva commented Oct 10, 2016 • edited Loading

chosroes commented Oct 13, 2016

filipesilva commented Oct 14, 2016

vinchauhan commented Oct 18, 2016

vinchauhan commented Oct 19, 2016

derailed commented Nov 3, 2016

doliver3 commented Nov 23, 2016

mayakwd commented Dec 12, 2016

JSMike commented Jan 12, 2017

valterbarros commented Feb 1, 2017

JSMike commented Feb 2, 2017 • edited Loading

valterbarros commented Feb 2, 2017

angular-automatic-lock-bot bot commented Sep 6, 2019

chosroes commented Sep 5, 2016 •

edited

Loading

chosroes commented Sep 5, 2016 •

edited

Loading

divid3byzero commented Sep 20, 2016 •

edited

Loading

MartinNuc commented Sep 25, 2016 •

edited

Loading

brianmadden commented Sep 27, 2016 •

edited

Loading

filipesilva commented Oct 10, 2016 •

edited

Loading

JSMike commented Feb 2, 2017 •

edited

Loading