webpack-federation-types-plugin 1.2.1 → 1.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/FederationTypesPlugin.js +0 -1
- package/package.json +1 -1
- package/TODO +0 -5
package/FederationTypesPlugin.js
CHANGED
|
@@ -158,7 +158,6 @@ class FederationTypesPlugin {
|
|
|
158
158
|
if (!declarationFileResponse) return
|
|
159
159
|
const declarationFileContent = declarationFileResponse.data
|
|
160
160
|
const decFilePath = path.join(remoteDeclareDirPath, moduleName)
|
|
161
|
-
fs.writeFile(decFilePath, declarationFileContent, {recursive: true})
|
|
162
161
|
fs.promises
|
|
163
162
|
.mkdir(path.dirname(decFilePath), {recursive: true})
|
|
164
163
|
.catch((error) => logger.error(`Failed to write dir: ${decFilePath}`, error))
|
package/package.json
CHANGED
package/TODO
DELETED
|
@@ -1,5 +0,0 @@
|
|
|
1
|
-
cts\wedding\node_modules\@types\appJAMain\getJAData.d.ts'
|
|
2
|
-
(Use `node --trace-warnings ...` to show where the warning was created)
|
|
3
|
-
(node:10492) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 15)
|
|
4
|
-
(node:10492) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
|
|
5
|
-
|