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

fix(types): fix global namespace declaration for UMD bundle #9912

Merged
merged 3 commits into from
Apr 25, 2019

Conversation

ktsn
Copy link
Member

@ktsn ktsn commented Apr 23, 2019

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

In the current declaration, index.d.ts has export as namespace Vue which exposes all exported types in index.d.ts in global namespace. So the user can access them by just writing like Vue.ComponentOptions without import statement.

But this declaration is actually not correct because the Vue constructor type is declared under default which is correct in ESModule bundle but UMD bundle.

new Vue({}) // This provides compilation error in current type.

new Vue.default({}) // No compilation error.

To declare Vue constructor as just Vue in global namespace, we need to write export as namespace Vue with a common js export. So I've add umd.d.ts and do that in that file.

@yyx990803
Copy link
Member

This should not affect existing usage with ES modules right?

@ktsn
Copy link
Member Author

ktsn commented Apr 25, 2019

Right, it should not affect. The entry point (index.d.ts) exports are the same and if a file is ES module, global Vue is not available.

@yyx990803 yyx990803 merged commit ab50e8e into vuejs:dev Apr 25, 2019
@ktsn ktsn deleted the fix-umd-global-declaration branch April 25, 2019 03:21
dukegod added a commit to dukegod/vue that referenced this pull request Jun 21, 2019
* commit 'bad3c326a3f8b8e0d3bcf07917dc0adf97c32351': (911 commits)
  chore: update sponsors [ci skip] (vuejs#10158)
  chore: fix sponsor url [ci skip]
  chore: update sponsors [ci skip] (vuejs#10136)
  chore: update sponsors [ci skip] (vuejs#10130)
  chore: update sponsors [ci skip] (vuejs#10113)
  chore(typo): fix comment typo (vuejs#10101)
  chore: update sponsors [ci skip] (vuejs#10064)
  Create FUNDING.yml
  chore: update sponsors [ci skip] (vuejs#10031)
  chore(typo): fix README tag mismatch (vuejs#9934)
  chore(typo): fix typo in comments (vuejs#9995)
  chore: update sponsors [ci skip] (vuejs#9970)
  chore: update sponsors [ci skip] (vuejs#9933)
  fix: fix function expression regex (vuejs#9922)
  fix(types): fix global namespace declaration for UMD bundle (vuejs#9912)
  fix(compiler): Remove the warning for valid v-slot value (vuejs#9917)
  polish: add warning when .native modifier is used on native HTML elements (vuejs#9884)
  test: fix running e2e test on windows (vuejs#9909)
  refactor: remove useless parameter to the function removeVnodes (vuejs#9914)
  test: separate failing test for TS 3.4
  ...

# Conflicts:
#	packages/weex-template-compiler/build.js
#	packages/weex-vue-framework/factory.js
#	packages/weex-vue-framework/index.js
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants