Source map not working for LESS files

[michael-letcher]

Versions

Angular CLI: 1.6.5
Node: 6.11.2
OS: darwin x64
Angular: 5.2.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.6.5
@angular-devkit/build-optimizer: 0.0.41
@angular-devkit/core: 0.0.28
@angular-devkit/schematics: 0.0.51
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.5
@schematics/angular: 0.1.16
typescript: 2.6.2
webpack: 3.10.0

Repro steps

• Run ng serve -sm -ec -env=mock
• Using Chrome inspector we see this

As you can see it seems to be everything imported via the CLI styles below are not being mapped while all the component LESS files are being mapped as expected.

Currently our step up is as follows:

"styles": [
  "app/shared/styles/bootstrap.less",
  "app/styles/main.less"
]

bootstrap.less, note the first import is to a custom less variables.less (copied from the repo). Component less is being

/ Core variables and mixins
@import "../../styles/bootstrap.variables.less";
@import "~bootstrap/less/mixins.less";

// Reset and dependencies
@import "~bootstrap/less/normalize.less";
@import "~bootstrap/less/print.less";

Example project (will have to download and place into full CLI to run command)

Observed behavior

Inspecting HTML in DevTools shows all the css is in styles.bundle.scss, where it used to display the scss source of the rule. So I can no longer determine where the css rule I am inspecting comes from.

Desired behavior

To see all less mappings and not just the components

Mention any other details that might be useful (optional)

Related to #9099 & #9235

[michael-letcher]

Checking in webpack:// I do not see any of my less source files.

Using const source = require('app/styles/main.less'); in main.ts

I see the single file now imported but all they have in them is:

// removed by extract-text-webpack-plugin

[michael-letcher]

Works in v7.3.x

[angular-automatic-lock-bot]

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.}