1

really hoping someone can point me in the right direction with this one as i'm having no luck at all. I'm trying to host a simple nodejs sveltekit application on a Windows based azure app service, but cannot get the application to start / run.

I'm using the adapter-node adapter for sveltekit to generate the build output as a self contained node app. After sveltekit generates the build output I inject a simple package.json file to the root of the build folder to instruct node to use the ESM style imports which simply contains a single property of type="module".

package.json

{ 
    "type": "module" 
}

Lastly I also inject a web.config into the root of the build folder for use with IISNode. The web.config file used is the same as from the nodejs quickstart guide provided by MS. The web.config can be seen here.

The final folder structure of the build output is simply:

build
└───assets
│   └───_app
│       │   ...
└───prerendered
│   index.js
│   package.json
│   web.config

Locally I can take this build folder, place it anywhere on my machine and it runs perfectly by simply running:

node index.js

The Problem

Even though it works perfectly locally, when I deploy the application to the Azure app service the application will not start with the browser simply displaying "This page isn’t working right now".

When I check the logs I see the following error:

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: D:\home\site\wwwroot\index.js
require() of ES modules is not supported.
require() of D:\home\site\wwwroot\index.js from D:\Program Files (x86)\iisnode\interceptor.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from D:\home\site\wwwroot\package.json.

The error tells me that MS's iisnode\interceptor.js is using the commonjs style require syntax and cannot import the ES module of my index.js.

I found someone having a similar problem and a suggested solution here. The suggested solution is to create a new file next to my index.js file and configuring it as the app service's (or more specifically iisnode's) entry point in the web.config. The new file would be named run.cjs and only contain the following:

import("./index.js");

I tried this option, adding the new run.cjs file and updating the web.config to set this as IISNodes entry point:

<add name="iisnode" path="run.cjs" verb="*" modules="iisnode"/>

When I try the site after doing this I get a new problem. The site now loads but instead of seeing the app, the js from index.js renders as raw text into the browser.

The azure app service WEBSITE_NODE_DEFAULT_VERSION is set to ~14 and I can see from Kudu that the version running is 14.16.0 - my local machine is 14.17.0 so the node version looks to be ok.

Can anyone help??

Thanks in advance

Kevinio
  • 11
  • 1

1 Answers1

0

Please re-install/update the npm module on your project. Make sure all these files are present in your project. Do not import your index.js file in other files like run.cjs or run.mjs, after building your application in your local and publish it in azure app service.

{ 
    "type": "module" 
}

This above code is required in the package.json file.

enter image description here

Check your npm reference files, if anyone of them is not installed properly, then you'll get the raw data which is present in app,js file, as output

SaiSakethGuduru
  • 2,218
  • 1
  • 5
  • 15