Docs don't mention minimum ES target version

[dxptqhtlutehvlyxcmtg]

Thanks for this package. It's proving to be very useful.

Is the document missing? Please describe.

I can't remember why now, but my tsconfig.json target happened to be set to ES2021 and while this library did run, it reported every field in my AppConfig class was missing, even though I verified they weren't.

Simply changed the target to ES2022 and the library works as expected. Perhaps it has something to do with the class property features introduced then.

It took me by surprise because a different library that seemingly operates similarly does not have a problem under ES2021.

So, if there is indeed a minimum ES version, it would save users some trouble if the docs made mention of it.

[Val-istar-Guo]

The compatibility has not been tested before, which caused you trouble.
And this is a really interesting issue!!! This is also the first time I have seen someone do something similar to me.

The problem was that I was using Object.getOwnPropertyNames to avoid adding decorators(like @Value in @itgorillaz/configify） to all properties:

npm.nestjs-config/src/config.module.ts

Lines 36 to 45 in 02fc772

	for (const key of Object.getOwnPropertyNames(instance)) {
	const configName = Reflect.getMetadata(CONFIG_NAME_METADATA_KEY, ConfigProviderClass, key)
	if (configName) {
	const value = objectPath.get(config, configName)
	if (value !== undefined) instance[key] = value
	}
	const value = subConfig && subConfig[toCamelCase(key)]
	if (value !== undefined) instance[key] = value
	}

However, this leads to the loss of these properties, in target=es2021.

I will try to solve this problem.