Vee-validate: error TS1036: Statements are not allowed in ambient contexts.

Created on 4 Jun 2018  Â·  5Comments  Â·  Source: logaretm/vee-validate

Versions

  • vee-validate: 2.1.0-beta.1
  • vue: 2.5.16

Describe the bug
node_modules/vee-validate/types/vee-validate.d.ts(163,2): error TS1036: Statements are not allowed in ambient contexts. will be printed when executing npx tsc --noEmit --allowSyntheticDefaultImports false

To Reproduce
Steps to reproduce the behavior:

  1. Create a new npm project
  2. Add typescript in Version 2.8.4
  3. Add vee-validate in Version 2.1.0-beta.1
  4. Add a tsconfig.json as descripted in Additional context
  5. Execute npx tsc --noEmit --allowSyntheticDefaultImports false

Expected behavior
node_modules/vee-validate/types/vee-validate.d.ts(163,2): error TS1036: Statements are not allowed in ambient contexts. will be printed when executing npx tsc --noEmit --allowSyntheticDefaultImports false

Desktop (please complete the following information):

  • OS: Linux (Ubuntu 18.04)

    • Node Version: 10.3.0

    • NPM Version: 6.1.0

    • Typescript Version: 2.8.4

Additional context
tsconfig.json

{
  "compilerOptions": {
    "target": "es5",
    "module": "esnext",
    "allowSyntheticDefaultImports": true,
    "moduleResolution": "node",
    "strict": true,
    "lib": [
      "esnext",
      "dom",
      "dom.iterable"
    ],
    "outDir": "built"
  },
  "include": [
    "./src/**/*.ts",
    "./src/**/*.vue"
  ],
  "exclude": [
    "./node_modules",
    "./built"
  ]
}

Most helpful comment

Unfortunately I Will not be able to publish a release until Sunday. Will
check if a team member can.

On Wed, 6 Jun 2018, 15:22 Luca Steeb, notifications@github.com wrote:

Thanks for fixing. Can you please publish on npm?

—
You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub
https://github.com/baianat/vee-validate/issues/1365#issuecomment-395066292,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-KSibT48KBXXwCkTmBbOJzwjzkBF9Vks5t59eLgaJpZM4UZJoG
.

All 5 comments

fixed by #1366

Thanks for fixing. Can you please publish on npm?

Unfortunately I Will not be able to publish a release until Sunday. Will
check if a team member can.

On Wed, 6 Jun 2018, 15:22 Luca Steeb, notifications@github.com wrote:

Thanks for fixing. Can you please publish on npm?

—
You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub
https://github.com/baianat/vee-validate/issues/1365#issuecomment-395066292,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-KSibT48KBXXwCkTmBbOJzwjzkBF9Vks5t59eLgaJpZM4UZJoG
.

It's been 10 days, long past Sunday, and this bug is still in npm's version. Can you please publish beta.2?

I'm currently serving in mandatory army service with no access to a pc, and
limited time off. So please understand that I cannot maintain this project
24/7 like I used to. I asked a college to tag a release today. So it should
be up soon.

On Sat, 16 Jun 2018, 20:16 ezaquarii, notifications@github.com wrote:

It's been 10 days, long past Sunday, and this bug is still in npm's
version. Can you please publish beta.2?

—
You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub
https://github.com/baianat/vee-validate/issues/1365#issuecomment-397830180,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-KSlQMhwah9G4mMX1bcV5SX-ng6fiLks5t9Ut5gaJpZM4UZJoG
.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

MaxMilton picture MaxMilton  Â·  3Comments

jagasan picture jagasan  Â·  3Comments

the94air picture the94air  Â·  3Comments

YamenSharaf picture YamenSharaf  Â·  3Comments

Shchepotin picture Shchepotin  Â·  3Comments