@rollup/plugin-html： How to use normally

[zhangmeiren]

When I use laya to compile, the following problems will occur. Do you know about this problem, or how to better set the publicpath in the laya compilation environment next time

[potatohoney-p]

The first screenshot shows Unknown object type "asyncfunction" inside rollup-plugin-typescript2. That points to its cache-key hashing of the Rollup configuration, rather than an invalid publicPath URL.

I reproduced that exact error with Rollup 1.32.1, rollup-plugin-typescript2 0.20.1, TypeScript 3.9.10 and @rollup/plugin-html 0.2.4. The HTML plugin has an async hook, which that older cache has trouble hashing.

For that reproduction, adding clean: true to the typescript2 options bypasses its cache and allows the build to finish:

plugins: [
  html({
    publicPath: 'https://example.invalid/assets/',
  }),
  typescript({
    tsconfig: workSpaceDir + '/tsconfig.json',
    clean: true,
  }),
]

This trades away the plugin's incremental cache, so builds may be slower. It doesn't require changing the public URL. The generated HTML in my test contained https://example.invalid/assets/main.js, and the generated JavaScript ran successfully.

There is also a documented objectHashIgnoreUnknownHack: true option, which passed the same reproduction. It can miss cache invalidation when ignored parts of the configuration change, so don't enable it without that caveat; the typescript2 README recommends clean builds, especially before release.

Those are pinned reproduction versions, not a recommendation to downgrade. I haven't run your LayaAir IDE environment, and its bundled plugin versions aren't shown in the screenshots. Check which typescript2 version Laya actually loads before applying the option; @rollup/plugin-typescript is a different plugin.