No way to specify absolute paths for ES6 imports

[gCardinal]

I might be wrong, but I could not find any way to make it work for me and the doc does not suggest that feature exists.

Currently, when I import, if I let the plugin autocomplete this import statement: import Person from 'app/Per, I will get import Person from 'Person.js' as my import. I would much rather have app/Person for refactoring reasons.

Maybe there could be an option in the plugin to tell it if we prefer absolute or relative paths?

[jballant]

I think this is already supported, unless I am not understanding your issue correctly.

If you go into the preferences menu and then navigate to "Other Settings" > "CommonJS AutoComplete" you will see a form with a checkbox that says "Use relative paths for files in Main JS Root Directory". If you uncheck that box, then the autocomplete paths will be path from the value of the "Main JS Root Directory Location" field to the matching files, and not relative to the current file.

So if your "Main JS Root Directory Location" value is "./src", relative to the project root, and the plugin finds a matching file in "<project_root>/src/path/to/Person.js", then your autocomplete value should be "path/to/Person".

If your js directory is the top project level directory, just leave the "Main JS Root Directory Location" field blank, and uncheck the "Use relative paths for files in Main JS Root Directory".

I hope this accomplishes what you are looking for.