The module declaration is triggering a lint error that reads "Unexpected token, expecting '{'"

Question

The module declaration is triggering a lint error that reads "Unexpected token, expecting '{'"

To address the absence of available types for a library, I created the file omnivore.d.ts in TypeScript. Within this file, I added the following line:

declare module '@mapbox/leaflet-omnivore'

Upon running vue-cli-service lint in my project, an error is raised specifically on that line:

Error: Parsing error: Unexpected token, expected "{"

> 1 | declare module '@mapbox/leaflet-omnivore'
    |                                          ^

Although the webpage functions properly without any issues, this lint error causes a failure in my continuous integration process. Despite searching and finding suggestions to add an object after the string, I remain unsure about what modification is needed in this scenario.

typescript

Answer 1

Answer №1

I updated the code to

declare module '@mapbox/leaflet-omnivore' {/* empty */}

This change aligns with eslint recommendations for empty blocks.

Answer 2

I updated the code to

declare module '@mapbox/leaflet-omnivore' {/* empty */}

This change aligns with eslint recommendations for empty blocks.

Answer 3

Answer №2

When I first started using lint-staged, this error popped up because I only specified the file extensions at the end *.{js, jsx, ts, tsx}, causing lint to check all files with those extensions.

Here's how I fixed it: Include the ! Operator before an extension to exclude it from linting:

Success!

{
 "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "lint-staged": {
    "*.{js,jsx,ts,tsx}, !*.d.{ts}": [
      "yarn run lint"
    ]
  }
}

Answer 4

When I first started using lint-staged, this error popped up because I only specified the file extensions at the end *.{js, jsx, ts, tsx}, causing lint to check all files with those extensions.

Here's how I fixed it: Include the ! Operator before an extension to exclude it from linting:

Success!

{
 "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "lint-staged": {
    "*.{js,jsx,ts,tsx}, !*.d.{ts}": [
      "yarn run lint"
    ]
  }
}

The module declaration is triggering a lint error that reads "Unexpected token, expecting '{'"

Answer №1

Answer №2

Similar questions

Using Typescript to iterate through an array of objects and modifying their keys using the forEach method

Excluding node modules when not included in tsconfig

In TypeScript, an interface property necessitates another property to be valid

Steps for utilizing response data as parameters for useInfiniteQueryHere is how you can make

Adding an image to a React component in your project

Error message in TypeScript: A dynamic property name must be a valid type such as 'string', 'number', 'symbol', or 'any'

I am seeking to modify the CSS of the parent component upon the loading of the child component in Angular

Issues arising with utilizing Github for hosting Angular applications

The attribute 'NameNews' is not recognized in the specified type when running ng build --prod

.Net Core receives the method name instead of the parameter value passed by TypeScript

Incorporate Ng-Survey multiple times within one component

Unable to set textAlign column property in Inovua React Data Grid using typescript

Aggregate the data chunks in the antd table into groups

Is there a way to revert my Ionic CLI back to the previous version that I had installed?

The error TS2300 arises from the duplicate identifier 'PropertyKey' found in the node_modules/@types/core-js/index.d.ts file

What causes the failure of $event binding when using RowGroup tables with PrimeNG?

The Google Sign-in feature is unable to access the property 'load' due to being undefined

Angular error TS2322 arises when attempting to assign a type of 'Observable<{}>' with the share() operator

What is the process for attaching an analytics tag to data messages using the Firebase Admin SDK with Javascript or TypeScript?

The property "state" of RouteComponentProps location does not exist in the provided type {}