aem-react icon indicating copy to clipboard operation
aem-react copied to clipboard

Compilation error with scripts

Open monalishah opened this issue 7 years ago • 1 comments

Hi,

I am facing compilation error while building the project. Build is success but scripts are not compiled successfully. Please find the error below:

ERROR in ./componentRegistry.tsx (10,45): error TS2345: Argument of type '{ component: typeof Panel; parsysPath: string; depth: number; }' is not assignable to parameter of type 'ComponentConfig'. Object literal may only specify known properties, and 'parsysPath' does not exist in type 'ComponentConfig'.

ERROR in C:\projects\react-poc\eon.com.react\ui.apps\src\main\ts\server.tsx (20,32): error TS2346: Supplied parameters do not match any signature of call target.

ERROR in ./client.tsx (14,28): error TS2346: Supplied parameters do not match any signature of call target. Webpack build for 'development' -> reactserver jcrpath 'C:\projects\react-poc\eon.com.react\ui.apps\target\classes\etc\designs\eon-com-react\clientlib-site env "production" ts-loader: Using [email protected] and C:\projects\react-poc\eon.com.react\ui.apps\src\main\ts\tsconfig.json Hash: 242d068f8068d0eb3521 Version: webpack 1.15.0 Time: 14448ms Asset Size Chunks Chunk Names reactserver.js 1.99 MB 0 [emitted] reactserver + 216 hidden modules

ERROR in ./componentRegistry.tsx (10,45): error TS2345: Argument of type '{ component: typeof Panel; parsysPath: string; depth: number; }' is not assignable to parameter of type 'ComponentConfig'. Object literal may only specify known properties, and 'parsysPath' does not exist in type 'ComponentConfig'.

ERROR in ./server.tsx (20,32): error TS2346: Supplied parameters do not match any signature of call target.

ERROR in C:\projects\react-poc\eon.com.react\ui.apps\src\main\ts\client.tsx (14,28): error TS2346: Supplied parameters do not match any signature of call target.

What could be wrong with the setup?

monalishah avatar Dec 11 '17 11:12 monalishah

type of ComponentConfig was changed. it is now

parsys: {path: '/....'}

instead of

parsysPath: '/....'

stemey avatar Dec 11 '17 12:12 stemey