You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to publish a sveltekit adapter to jsr, but I have encountered a problem. The adapter relies on some js files (shims.js & lambda-handler.js) that serve as the basis for the adapter and are compiled by the adapter itself (using esbuild). When I upload the js files, jsr modifies their imports (probably because they are not specified in the package.json) by converting them to deno-like paths, for example:
These files are not part of the package's js code and are not intended to be included or processed in this way. Instead, they are like assets that need to be included in the package.
Is there a way to include those js files in the package without processing them?
The text was updated successfully, but these errors were encountered:
I am trying to publish a sveltekit adapter to jsr, but I have encountered a problem. The adapter relies on some js files (shims.js & lambda-handler.js) that serve as the basis for the adapter and are compiled by the adapter itself (using esbuild). When I upload the js files, jsr modifies their imports (probably because they are not specified in the
package.json
) by converting them to deno-like paths, for example:It also adds
./
prefix to my import macros:These files are not part of the package's js code and are not intended to be included or processed in this way. Instead, they are like assets that need to be included in the package.
Is there a way to include those js files in the package without processing them?
The text was updated successfully, but these errors were encountered: