How to install serverless on an ubuntu server - serverless-framework

I am trying to deploy lambda code, using aws serverless.
I am using a Virtual private server for that task, and i cannot properly run the serverless command. Each time, he throw me this error :
/usr/local/lib/node_modules/serverless/node_modules/essentials/index.js:21
throw reason;
^
ReferenceError: navigator is not defined
at getChromeVersion (/usr/local/lib/node_modules/serverless/node_modules/supports-color/browser.js:5:68)
at Object.<anonymous> (/usr/local/lib/node_modules/serverless/node_modules/supports-color/browser.js:14:22)
I have installed chromium, and the 'google-chrome-stable' package, but without success.
Someone can help me ?
Renaud

Related

Cannot use import statement outside a module when using wrangler v2

I'm new to using cloudflare and wrangler. I've a project that I've been working on, and I'm now trying to deploy it using wrangler publish, but I keep running into issues. My product is coded in node.js, and I'm using version 2 of wrangler. When I execute wrangler publish I get:
Basic JavaScript project found. Skipping unnecessary build!
Error: Something went wrong with the request to Cloudflare...
Uncaught SyntaxError: Cannot use import statement outside a module
at worker.js:2Basic JavaScript project found. Skipping unnecessary build!
Error: Something went wrong with the request to Cloudflare...
Uncaught SyntaxError: Cannot use import statement outside a module
at worker.js:2
I've searched for a solution, and one of them that I found said to change module in wrangler.toml from type="javascript"to type="webpack" however that gives me a bunch of errors:
./node_modules/destroy/index.js
Module not found: Error: Can't resolve 'fs' ... Parsed request is a module...resolve as module
/Users/Desktop/APIs/cpiCalculator2/node_modules/destroy/node_modules doesn't exist or is not a directory
...
Error: webpack returned an error. You may be able to resolve this issue by running npm install.
I've tried reinstalling npm as it suggests and then wrangler publish again, but that just gives me the same error message.
I'm really not sure what the issue is, and I would really appreciate any help or advice on how to resolve this issue. Thank you!
Also, just a note, I'm not sure if this is affecting it, but I do have two other js documents in the main area of my project (where my index.js file is).

After SvelteKit Migration Server Index.js not found

So I am trying to migrate my SvelteKit project with this migration guide:
https://github.com/sveltejs/kit/discussions/5774
I updated to sveltekit version 1.0.0-next.405 and my app works fine.
I then execute `
npx svelte-migrate routes
and it executes fine. I have the new folder structure in my project.
I searched the codebase for #migration and "migration" but found no other files with to-dos.
So I am trying a npm install && npm run dev and get the following error
404
Not found: /
Error: Not found: /
at resolve (file:///home/yannick/Downloads/test%20migration/.svelte-kit/runtime/server/index.js:3523:14)
at async Object.handle (//home/yannick/Downloads/test migration/src/hooks:8:19)
at async respond (file:///home/yannick/Downloads/test%20migration/.svelte-kit/runtime/server/index.js:3402:20)
at async file:///home/yannick/Downloads/test%20migration/node_modules/#sveltejs/kit/dist/vite.js:1539:22
did I miss a step during migration?
Went to all the folders described in the error and could not find any more hints.
I think it was just because I did not update to .406 after migration
Comment here describes how it is done
https://stackoverflow.com/a/73578603/12505487

MWAA Airflow UI: Broken plugin[No module]

I have created Airflow environment in MWAA. I have mentioned all the required modules in requirements.txt but getting 'Broken plugin: No module found' error in MWAA Airflow UI although Scheduler/worker logs show modules are installed successfully and dags using those modules are also working fine.
Does anyone have any idea, How to get rid of this error?
UI Error
Scheduler logs

Cannot find module '../.../app/constants' when running npx #adobe/reactor-sandbox

I'm developing an extension in the Adobe Launch API, and everything was working fine with the command until this morning. Now when I run it, I receive the following error.
internal/modules/cjs/loader.js:883
throw err;
^
Error: Cannot find module '../../app/constants'
Require stack:
- D:\coding_projects\node_modules\#adobe\reactor-sandbox\src\tasks\constants\files.js
- D:\coding_projects\node_modules\#adobe\reactor-sandbox\src\tasks\helpers\getExtensionDescriptor.js
- D:\coding_projects\node_modules\#adobe\reactor-sandbox\src\tasks\run.js
- D:\coding_projects\node_modules\#adobe\reactor-sandbox\src\cli.js
I've tried reinstalling the individual package, as well as running npm install as a whole. My project has never contained a
../../app/constants
and has worked before without this error. Any ideas?

Meteor application not deploying, Errors prevented startup

I cloned the rocket chat repo on GitHub and ran meteor npm install && meteor, it wasn't able to deploy the app and got stuck, so I exited and tried meteor but it throws the same error:
Errors prevented startup:
While loading plugin `Livechat` from package `rocketchat:livechat`:
child_process.js:635:11: Command failed: C:\web dev\RocketChat\Rocket.Chat\packages\rocketchat-livechat\plugin/build.bat
'C:\web' is not recognized as an internal or external command,
operable program or batch file.
at checkExecSyncError (child_process.js:635:11)
at execSync (child_process.js:671:15)
at module (packages/Livechat/plugin/build-livechat.js:20:2)
at fileEvaluate (packages/modules-runtime.js:336:7)
at Module.require (packages/modules-runtime.js:238:14)
at require (packages/modules-runtime.js:258:21)
at <runJavaScript-36>:94:1
at <runJavaScript-36>:99:3
Your application has errors. Waiting for file change.
Started MongoDB.
And gets stuck there.
The issue here is with the space in the name of your web deb folder. This should probably be compensated for in the package code, but since it isn't the easiest solution would be to rename your folder to not have a space in the name and then maybe file a issue in the appropriate repo.