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
D:\Projects\vacuumlabs\adalite>yarn install
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
$ cd app && yarn install && cd ..
yarn install v1.22.19
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.23s.
Done in 63.99s.
D:\Projects\vacuumlabs\adalite>yarn build
yarn run v1.22.19
$ NODE_ENV=production webpack --progress --config webpack.build.config.js
'NODE_ENV' is not recognized as an internal or external command,
operable program or batch file.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Secure Connection Failed
An error occurred during a connection to localhost:3000. SSL received a record that exceeded the maximum permissible length.
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
This site can’t provide a secure connectionlocalhost sent an invalid response.
[Try running Windows Network Diagnostics](javascript:diagnoseErrors()).
ERR_SSL_PROTOCOL_ERROR
Perhaps you can make it possible to build on Windows right out of the box.
And for the SSL error, unclear to me how to open http page. Browsers do not allow this. They want to open https page, perhaps because adalite still poses as a https page when it should not?
Attempting to launch with ADALITE_ENABLE_HTTPS=true will fail.
yarn run v1.22.19
$ NODE_ENV=production & node server/index.js
'NODE_ENV' is not recognized as an internal or external command,
operable program or batch file.
<i> [webpack-dev-middleware] wait until bundle finished
node:internal/fs/utils:348
throw err;
^
Error: ENOENT: no such file or directory, open 'server.cert'
at Object.openSync (node:fs:600:3)
at Object.readFileSync (node:fs:468:35)
at Object.<anonymous> (D:\Projects\vacuumlabs\adalite\server\index.js:177:14)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Module._load (node:internal/modules/cjs/loader:878:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:23:47 {
errno: -4058,
syscall: 'open',
code: 'ENOENT',
path: 'server.cert'
}
Node.js v18.12.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
The text was updated successfully, but these errors were encountered:
sorry for the late reply, the preferred way to run the project locally is using yarn dev which I'd expect to work fine even on Windows.
When it comes to the browser HTTPS errors when ENABLE_LOCAL_HTTPS is set to true, this flag shouldn't really be used in production mode, only in development and then a self-signed HTTPS certificate is used. The browsers may still "complain" that the certificate is invalid, but they should allow you through by clicking "proceed anyway" or a similar button that would be visible on the error page
For the best windows development experience I'd recommend using WSL https://ubuntu.com/desktop/wsl which should remove any environment-specific incompatibilities this project has, given it is being developed and hosted on UNIX environments
Using
Windows 10
yarn v1.22.19
node-v18.12.0-x64
I searched for NODE_ENV error title:
https://stackoverflow.com/questions/11928013/node-env-is-not-recognized-as-an-internal-or-external-command-operable-comman
I added & symbol to package.json as per stackoverflow comments:
It then builds and starts like so:
Opening https://localhost:3000/ in Firefox reports:
Opening https://localhost:3000/ in Chrome reports:
Perhaps you can make it possible to build on Windows right out of the box.
And for the SSL error, unclear to me how to open http page. Browsers do not allow this. They want to open https page, perhaps because adalite still poses as a https page when it should not?
Attempting to launch with ADALITE_ENABLE_HTTPS=true will fail.
The text was updated successfully, but these errors were encountered: