convert relative filepath for security reason

[Jxck]

power-asserted test result includes filepath with 'full path' like this.

assert.strictEqual(assert._expr(assert._capt(typeof res, 'arguments/0'), {
  content: 'assert.strictEqual(typeof name, \'string\')',
  filepath: '/home/username/path/to/project/and/file.js',
  line: 22
}), 'string');

file path with full path is kind of sensitive information in server or developer machine.
if user doesn't know this behavior, it may cause some security issue.
(for example, some could forgot adding build result to gitignore and push to public repository.)

I think this information is only a project specific.
so it seems better for me to use relative path of test file or project or configurable base bath.

any comments ?

[twada]

@Jxck Thank you for your comment. You are absolutely right.

Using relative paths is already planned in next release, but now I'm reminded I have to hurry.

• Duplication in the error's stack and message
• sourceRoot option

I'm so sorry for my insensitiveness. Next version will be released soon.
Thank you so much.

[Jxck]

thanks, close this when resolved.

[Jxck]

it seems some commits but not fixed yet in current version
any updates or not ?

[twada]

@Jxck Sorry for slow progress. power-assert is now in 1.0.0 release process. To be released today or tomorrow.

[Jxck]

🙏🍻🍻🍻🙏

[twada]

@Jxck, instrumentors below are using ^1.0.0 of espower (or espower-source) module so they have fixed. You don't need to update power-assert, but need to upgrade one of them you are using now.

• espower-loader
• intelli-espower-loader
• espower-cli
• espowerify
• grunt-espower
• gulp-espower
• espower-coffee
• babel-plugin-espower
• webpack-espower-loader.
• espower-typescript
• espower-babel
• espower-traceur

More to come (PRs are already proposed):

• karma-espower-preprocessor

[twada]

This issue is fixed by the 1.0.0 release of power-assert family.
Feel free to reopen this if it is not fixed.

[Jxck]

great work thanks :)