cannot require files with dynamic path anymore

Asked Nov 29 '16 at 04:12

Active Mar 07 '17 at 05:55

Viewed 195 times

We used to be able to to do this :

    let path = 'test.component.ts';
    let file = require('./path/to/file/'+path);
    console.log('file',file);

But this is not working any more with the latest cli.

This works :

    let file = require('./path/to/file/test.component.ts');
    console.log('file',file);

So basically , webpack wont let me require file dynamically anymore in cli .

edited Dec 29 '16 at 21:38

asked Nov 29 '16 at 04:12

Milad

you should change it with var path = '' – Saeed Dec 21 '16 at 15:31
@SaeedPy What ? – Milad Dec 21 '16 at 22:41
change {let} with {var} – Saeed Dec 22 '16 at 09:25
are you using `AOT` ? – Ankit Singh Dec 27 '16 at 08:33
@AnkitSingh , no I'm not , but does it matter? – Milad Dec 27 '16 at 08:35
yes, AFAIK AoT allows only static values for now, which means `require('./path/to/file/'+path);` can't be resolved because `path` makes it dynamic. I had this issue with dynamic variables in `template` ie `
${someVar}
` – Ankit Singh Dec 27 '16 at 08:37
@AnkitSingh , I've been looking into their code and I realised they've created a buggy loader which does all this hacks , I'm not using AOT now, but even if I do , I should work. – Milad Dec 27 '16 at 08:41
yeah, I hvn't used `ng cli` much, maybe loader is at fault. is there any error btw ? – Ankit Singh Dec 27 '16 at 08:43
Isn't ng cli using AOT for their production builds now? Also dynamic requires doesn't make it easy for tree-shaking, so it should be considered a good thing that this doesn't work also in dev mode. – Peter Salomonsen Dec 27 '16 at 21:26

${someVar}