Use classes do not allow for paths outside of current folder about htlengine HOT 7 CLOSED

thanks, I will look into it as soon as I have time....

from htlengine.

I think the update from 3.2.7 to 3.2.8 should have had a major version bump.

yes. you're probably right.

the use classes now follow the nodejs require semantic. if the name doesn't start with a ./, it is considered a global module, otherwise it is relative to the htl file. I think the bug here is that it doesn't check for ../. so you could try to reference it with ./../modules/com.companyname.project.InlineSvgUtility.js, depending where your .htl is.

another possibility could be to add the src/modules path to the module path when running your script. maybe you can play around with NODE_PATH.

@struct78 any chance our source code is public?

from htlengine.

@tripodsan Unfortunately not. I'll try and make a public repo with some sample code if I get the time.

from htlengine.

@tripodsan Here is some sample code that closely matches our setup https://github.com/struct78/htlengine-issue-114

from htlengine.

ok, I see the problem. you are using the compileToFunction() which fakes the module and uses the require of the compiler.

from htlengine.

nodejs 10.12 added: https://nodejs.org/docs/latest-v10.x/api/modules.html#modules_module_createrequirefrompath_filename

which would be an easy way to add the useDirectory to the module paths...

from htlengine.

🎉 This issue has been resolved in version 3.3.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from htlengine.