Skip to content
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

Should we expose separate methods on default export? #6

Open
tunnckoCore opened this issue Mar 17, 2017 · 1 comment
Open

Should we expose separate methods on default export? #6

tunnckoCore opened this issue Mar 17, 2017 · 1 comment

Comments

@tunnckoCore
Copy link
Member

Like that

const dush = () => {
  // ... code
}

const app = dush()
app.dush = dush

export default app

so we can just

const { on, off, once, emit, use } = require('dush')

or get the singleton

const { dush } = require('dush')
@tunnckoCore
Copy link
Member Author

tunnckoCore commented Mar 19, 2017

Actually... why? Don see fit for this, so it won't land until anyone want it. Ping me if you want to do it.

edit: I'll leave that open for feedback.

@tunnckoCore tunnckoCore reopened this Mar 19, 2017
@tunnckoCore tunnckoCore changed the title [Semver: Marjor][v3] Expose separate methods on default export Should we expose separate methods on default export? Mar 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant