Anyone know if it’s possible to use the `@NAmdConf...
# suitescript
m
Anyone know if it’s possible to use the
@NAmdConfig
tag to import non-AMD modules in a custom module? My config seems to work fine when added directly to a script, but things seem to fall apart when it’s added to a custom module.
s
as far as I know this is a (showstopper imho) limitation of NS @NAmdConfig support
I just resort to using relative path names in both top level scripts and custom modules to avoid confusion.
m
yeah, i gave up trying to make it work and restructured (in a less reusable way) the code. Thanks for the confirmation though!
s
aye, maybe suitescript 2.1? will improve that
m
🤞