-
Notifications
You must be signed in to change notification settings - Fork 12
fix!: add named exports for global-config utils #359
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
fix!: add named exports for global-config utils #359
Conversation
|
@keanu-a since this changes what's exported from the package, this is technically a breaking change, so let's rename the PR to start with |
packages/dev-utils/src/main.ts
Outdated
| export { ensureNetlifyIgnore } from './lib/gitignore.js' | ||
| export { headers, toMultiValueHeaders } from './lib/headers.js' | ||
| export * as globalConfig from './lib/global-config.js' | ||
| export { default as getGlobalConfigStore, GlobalConfigStore, resetConfigCache } from './lib/global-config.js' |
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.
sorry for churning, but now that I look at it... maybe we can just change the ./lib/global-config module to export getGlobalConfigStore as a named export instead of a default export? it's a little weird as is, and we're here making a breaking change anyway
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.
No its okay! I agree with changing the default export. Changed to named export
serhalp
left a comment
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.
LGTM
Switched from namespace export of
global-configutils to explicit named exports