use extension in relative imports

[jimmywarting]

swagger-js/src/index.js

Lines 3 to 8 in ba0db61

	import Http, { makeHttp, serializeRes, serializeHeaders } from './http';
	import Resolver, { clearCache } from './resolver';
	import resolveSubtree from './subtree-resolver';
	import { makeApisTagOperation } from './interfaces';
	import { execute, buildRequest, baseUrl } from './execute';
	import { opId } from './helpers';

extension less is a bit non-esm ish way of doing things

[char0n]

Justyfication: https://nodejs.org/api/esm.html#esm_mandatory_file_extensions

[jimmywarting]

I'm guess the only reason why this still work without extension is b/c you transpile it to cjs for compability?

[char0n]

@jimmywarting exactly, CJS is just one of the transpiled form. Mapping of build fragments is explicitly defined in package.json:

https://github.com/swagger-api/swagger-js/blob/master/package.json#L10

[swagger-bot]

🎉 This issue has been resolved in version 3.18.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀