Environement files generated twice when changing sourceDir parameter

[maxailloud]

Hi there,

After sawing this Pull Request #412 I wanted to give it a try.
So I made a change in my angular-cli-build.js file:

/* global require, module */

var Angular2App = require('angular-cli/lib/broccoli/angular2-app');

module.exports = function(defaults) {
 return new Angular2App(defaults, {
 vendorNpmFiles: [],
 sourceDir: 'src'
 });
};

Just added the sourceDir parameter.

It's working great, now I don't have the client folder that I was useless to me.
But the environement.js file is still copied in the build/client/app folder.
So I end up having 2 environement.js file, in the right folder build/appand in the wrong, that should not exist, folder build/client/app/.

FYI:

Mac OSX El Capitan
angular-cli: 0.0.33
node: 5.0.0
os: darwin x64

[filipesilva]

Ah that is entirely my fault. Will fix it asap.

On Tue, 26 Apr 2016, 11:25 Maxime Ailloud, notifications@github.com wrote:

Hi there,

After sawing this Pull Request #412
#412 I wanted to give it a
try.
So I made a change in my angular-cli-build.js file:

/* global require, module */
var Angular2App = require('angular-cli/lib/broccoli/angular2-app');
module.exports = function(defaults) {
return new Angular2App(defaults, {
vendorNpmFiles: [],
sourceDir: 'src'
});
};

Just added the sourceDir parameter.

It's working great, now I don't have the client folder that I was useless
to me.
But the environement.js file is still copied in the build/client/app
folder.
So I end up having 2 environement.js file, in the right folder build/appand
in the wrong, that should not exist, folder build/client/app/.

FYI:

Mac OSX El Capitan
angular-cli: 0.0.33
node: 5.0.0
os: darwin x64

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#530

[maxailloud]

Ok, thank you.

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