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

Exports Option #66

Closed
blond opened this issue Aug 14, 2015 · 0 comments
Closed

Exports Option #66

blond opened this issue Aug 14, 2015 · 0 comments
Assignees
Milestone

Comments

@blond
Copy link
Member

blond commented Aug 14, 2015

The ability to choose environment for i18n bundle. By default it exports to all environments: CommonJS, YModules, and if nothing to global scope.

For, examples, if need exports to global scope only:

exports: {
    globals: true,
    commonJS: false,
    ym: false
}

To force exports to global scope in CommonJS or Ymodules you can use force value:

exports: {
    globals: 'force',
    commonJS: true
}
@blond blond self-assigned this Aug 14, 2015
@blond blond added this to the 1.0.0 milestone Aug 14, 2015
@blond blond added the ready label Aug 17, 2015
@blond blond assigned tormozz48 and unassigned blond Aug 17, 2015
tormozz48 added a commit that referenced this issue Aug 17, 2015
tormozz48 added a commit that referenced this issue Aug 17, 2015
tormozz48 added a commit that referenced this issue Aug 17, 2015
@blond blond closed this as completed in #67 Aug 17, 2015
blond added a commit that referenced this issue Aug 17, 2015
#66 Add exports option to i18n technology
@blond blond removed the review label Aug 17, 2015
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

2 participants