`ignoreUnimported` does not work with relative paths as of 1.20.0

When using unimported version 1.20.0, it seems only absolute file paths are supported for the ignoreUnimported setting. I noticed this when, after updating, I was suddenly getting unimported errors for files that were previously being ignored. Running npx unimported -u only adds absolute paths to the config file, and changing them to relative paths causes them to stop working.

This is not only a breaking change with previous versions of .unimportedrs.json, but also causes issues when sharing config across team members.

Tested on Windows 10 with a Meteor project using Meteor version 2.7.1. I’m not sure if this replicates across other types of projects, or if it’s a meteor-specific issue.

[LandGod]

Ran again on windows with the update and it’s looking great. Thank you 😄

{
  "ignoreUnresolved": [],
  "ignoreUnused": [],
  "ignoreUnimported": [
    "dangling.js"
  ]
}

[smeijer]

Ok, I’ve updated the GitHub action to also run test cases on Windows, which indeed failed miserably. Then I added some fixes, and now I have all green flags.