ESM build not updated

[fa-sharp]

Hey team! I noticed that the flag_name property was missing in flagged transactions when using the SDK, and it seems the underlying issue is that the ESM build (under the dist/esm folder) is not being updated for some reason. This causes ESM bundlers like Parcel to end up with an older version of the SDK. For example, the following file in the ESM build is missing the flag_name property, which means the property won't be parsed:

ynab-sdk-js/dist/esm/models/TransactionDetail.js

Lines 60 to 62 in 7cda942

	'approved': json['approved'],
	'flag_color': !exists(json, 'flag_color') ? undefined : TransactionFlagColorFromJSON(json['flag_color']),
	'account_id': json['account_id'],

The flag_name property does appear in the Common JS build:

ynab-sdk-js/dist/models/TransactionDetail.js

Lines 67 to 70 in 7cda942

	'approved': json['approved'],
	'flag_color': json['flag_color'] == null ? undefined : (0, TransactionFlagColor_1.TransactionFlagColorFromJSON)(json['flag_color']),
	'flag_name': json['flag_name'] == null ? undefined : json['flag_name'],
	'account_id': json['account_id'],

Could you take a look? I'm guessing it might have something to do with the OpenAPI Generator that's being used. Let me know if you need more info or if I can help in any way!

[fa-sharp]

Did some more digging and I think I found the issue - it's the tsBuildInfoFile property in the tsconfig file. The ESM tsconfig needs a separate file for incremental compilation, otherwise it won't generate the new ESM files.

I added "tsBuildInfoFile": "./tsconfig.esm.tsbuildinfo" to the ESM tsconfig file:

ynab-sdk-js/src/tsconfig.esm.json

Lines 5 to 8 in 7cda942

	"module": "ES2015",
	"outDir": "../dist/esm",
	"moduleResolution": "node"
	}

Then when running the build command, the new ESM files are built as expected in the dist/esm folder.

The generated tsconfig.esm.tsbuildinfo file will also need to be added to .gitignore.

Hope that fixes this, but let me know if you need anything else!

[bradymholt]

Thanks for the report and help here @fa-sharp ! I've incorporated this fix in #175.