you probably need to adjust paths in `webpack.config.d/webpack.js`

# kvision

[Robert Jaros]

you probably need to adjust paths in webpack.config.d/webpack.js

[jschneider]

Ok. I am taking a look! Thanks for the hin!

[Robert Jaros]

I'm not sure what would be the correct starting point of resolving this path

[Robert Jaros]

probably somewhere in root/build/js/project/

[Robert Jaros]

try to experiment

[jschneider]

There is "../../" at the beginning. Do you have an idea why you added this?

[Robert Jaros]

it's relative to the directory webpack is run

[Robert Jaros]

in your case it could be necessary to exit to the root with additional ../ and than go inside a subproject build directory

[jschneider]

I think I require this prefix:

../../../../../

...

[jschneider]

5 dir backwards will end in the project root

[Robert Jaros]

you can probably use absolute path name if you like 🙂

[jschneider]

And it is working 👍👍👍

[jschneider]

--> absolute paths are not possible. It has to run on other machines, too

[jschneider]

It also works with:

config.resolve.modules.push(".");

[jschneider]

In this case the files from "build/js/packages/..." are used. Is this also possible? Any disadvantages?

[Robert Jaros]

webpack doesn't care what paths are added - you just have to make sure the files you require are in those paths

[jschneider]

I am thinking, that maybe "." could work in the template, too?

[jschneider]

It seems. At least for me it did. Maybe this is a better/simpler default? That works for more cases?

[Robert Jaros]

It really does! 🙂 Something changed in the Kotlin plugin since I last tested these options.

[Robert Jaros]

a "." is only working with IR, it does not with legacy compiler

[jschneider]

Aah. Ok. That might explain it.