-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extends Config/Plugin for Deno packaging #504
base: main
Are you sure you want to change the base?
Extends Config/Plugin for Deno packaging #504
Conversation
Thanks for the contribution! Before we can merge this, we need @AndresPrez to sign the Salesforce.com Contributor License Agreement. |
debug('config')('loadJSON %s', path) | ||
// Allows reading JSON with comments | ||
const _JSON = path.extname(_path) === '.jsonc' ? JSON5 : JSON |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thinking out loud here, maybe using dynamic imports here (so json5 isn't loaded by json users) might be kind.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, although it seems salesforce ppl have lost interest in supporting Deno
Tackles the
oclif/core
part for #503.It paves the way to start supporting deno projects. It essentially extends the logic around using the
package.json
as the project's root config file to also support Deno'sdeno.jsonc
configuration file.