We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When defining Typescript remotes we can set a path for mf-manifest.json but types are always created in dist without a sub path.
Withing modernjs server those files cannot be accessed. Please enable a param for dts like for manifest
name: 'my_provider', exposes: { './Container': './src/components/MyContainer.tsx', }, manifest: { filePath: '/modules/container/static/js', }, dts: { generateTypes: { typesPath: '/modules/container/static/js typesFolder: 'mf-container-types', }, }, shared: ['react', 'react-dom'], }),
Use the same path as given for mf-manifest.json by default and enable developers to define a custom path via dts generateTypes.typesPath
provide the types in js asset folder
No response
The text was updated successfully, but these errors were encountered:
Stale issue message
Sorry, something went wrong.
#2550 fixed this :)
2heal1
No branches or pull requests
Clear and concise description of the problem
When defining Typescript remotes we can set a path for mf-manifest.json but types are always created in dist without a sub path.
Withing modernjs server those files cannot be accessed.
Please enable a param for dts like for manifest
Suggested solution
Use the same path as given for mf-manifest.json by default and enable developers to define a custom path via
dts generateTypes.typesPath
Alternative
provide the types in js asset folder
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: