Rc-apps package fails on windows on seemingly simple import

cYzzie · March 5, 2022, 12:56am

i am trying to import a simple configuration object to star app configuration

like this:
import { ParserConfig } from “./config/ParserConfig”;

with the imported file looking like that

export abstract class ParserConfig {

public static apiBaseUrl: string = 'some url';

}

before i tried importing a handler class that i wanted to method export PreMessageSentHandler to, in both cases in my windows based development system the rc-package process fails with

Error: Build failed with 1 error:
C:/Users/username/AppData/Roaming/nvm/v14.18.3/node_modules/@rocket.chat/apps-cli/node_modules/@rocket.chat/apps-compiler/bundler/esbuild.js:47:92: error: [plugin: apps-engine] The “path” argument must be of type string. Received undefined

what am i doing wrong? is this a windows specific issue somehow?

cYzzie · March 7, 2022, 4:38am

apparently this is a bug

github.com/RocketChat/Rocket.Chat.Apps-cli

Error while Packaging simple App - The "path" argument must be of type string. Received undefined

opened 06:37PM - 22 Nov 21 UTC

JNBG

Tried building my first App. Followed the Tutorial [here](https://developer.rock…et.chat/apps-engine/getting-started/creating-an-app) All went well until adding a Slash Command and then packaging the App. On using the `rc-apps deploy` Command the App breaks on packaging with following Error: ``` PS C:\Users\49179\VSCProjects\testapp> rc-apps deploy Starting App Deployment to Server Getting Server Info... ✓ Packaging the app... - > ../../AppData/Roaming/npm/node_modules/@rocket.chat/apps-cli/node_modules/@rocket.chat/apps-compiler/bundler/esbuild.js:47:92: error: [plugin: apps-engine] The "path" argument must be of type string. Received undefined 47 │ if (!/@rocket\.chat\/apps-engine/.test(args.path) && path_1.default.isAbsolute(nodeModulePath)) { ╵ ^ at validateString (internal/validators.js:120:11) at Object.isAbsolute (path.js:353:5) at C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\@rocket.chat\apps-compiler\bundler\esbuild.js:47:93 at callback (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:814:34) at handleRequest (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:646:36) at handleIncomingPacket (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:701:7) at Socket.readFromStdout (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:578:7) at Socket.emit (events.js:315:20) at addChunk (_stream_readable.js:295:12) at readableAddChunk (_stream_readable.js:271:9) ../../AppData/Roaming/npm/node_modules/@rocket.chat/apps-cli/node_modules/@rocket.chat/apps-compiler/bundler/esbuild.js:35:26: note: This error came from the "onResolve" callback registered here 35 │ build.onResolve({ filter: /.*/ }, async (args) => { ╵ ~~~~~~~~~ at setup (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\@rocket.chat\apps-compiler\bundler\esbuild.js:35:27) at handlePlugins (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:738:23) at Object.buildOrServe (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:1026:7) at C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:1801:17 at new Promise (<anonymous>) at Object.build (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:1800:14) at Object.build (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:1655:51) at AppsCompiler.bundleCompilation [as bundler] (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\@rocket.chat\apps-compiler\bundler\esbuild.js:14:41) at AppsCompiler.bundle (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\@rocket.chat\apps-compiler\AppsCompiler.js:41:45) LiftoffApp.js:5:26: note: The plugin "apps-engine" was triggered by this import 5 │ const liftoff_1 = require("./commands/liftoff"); ╵ ~~~~~~~~~~~~~~~~~~~~ Error: Cannot find module './commands/liftoff' Require stack: - C:\Users\49179\VSCProjects\testapp/app.json at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15) at Function.resolve (internal/modules/cjs/helpers.js:78:19) ) at C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\@rocket.chat\apps-compiler\bundler\esbuild.js:46:58 at callback (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:814:34) at handleRequest (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:646:36) at handleIncomingPacket (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:701:7) at Socket.readFromStdout (C:\Users\49179\AppData\Roaming\npm\node_modules\@rocket.chat\apps-cli\node_modules\esbuild\lib\main.js:578:7) at Socket.emit (events.js:315:20) code: 'MODULE_NOT_FOUND', requireStack: [ 'C:\\Users\\49179\\VSCProjects\\testapp/app.json' ] } Packaging the app... ✖ » Error: ⟿ Build failed with 1 error: » ../../AppData/Roaming/npm/node_modules/@rocket.chat/apps-cli/node_modules/@rocket.chat/apps-compiler/bundler/esbuild.js:47:92: error: [plugin: apps-engine] The "path" argument must be of type » string. Received undefined ``` Whenever I remove the part where it's extending the Configuration for the Slash Command everything runs well and get's uploaded to my test-server. ```TypeScript protected async extendConfiguration(configuration: IConfigurationExtend): Promise<void> { await configuration.slashCommands.provideSlashCommand(new LiftoffCommand(this)); } ``` The LiftoffCommand is 1:1 Copy from the Tutorial. I am running this on: @rocket.chat/apps-cli/1.10.1 win32-x64 node-v12.18.1 You can find a reproduction Repo [here](https://github.com/JNBG/rcappstestapp)

mustafahasankhan · March 16, 2022, 2:16pm

Did you manage to find a fix for it?

cYzzie · March 16, 2022, 4:46pm

no its a bug … you can work around it using WSL (windows linux subsytem) but the build process then is 10 times slower then when using native node/rc-apps on windows

mustafahasankhan · March 17, 2022, 6:16am

Please can you share me your workaround for that? Seems like I’m still stuck there.

igorich · May 31, 2022, 4:51am

Topic		Replies	Views
Error compiling Rocket Chat Marketplace App Community Support	4	1323	February 4, 2019
Rc-apps package don't accept my imports Development rocketchat-apps	6	727	November 9, 2021
Error: Deployment error: No App found by the id Rocket.Chat Apps	1	1316	December 17, 2018
Rocket.Chat server not finding Node modules imported by an app Rocket.Chat Apps	2	2464	December 8, 2020
O.sort is not a function Rocket.Chat Apps	4	1538	May 10, 2019

Join our Community Open Call tomorrow where we'll share more details regarding recent changes and answer questions about updating your workspace to the latest Rocket.Chat

Rc-apps package fails on windows on seemingly simple import

bk201 posted a solution in the issue comments. It works for me.

Join our Community Open Call tomorrow where we'll share more details regarding recent changes and answer questions about updating your workspace to the latest Rocket.Chat

Rc-apps package fails on windows on seemingly simple import

bk201 posted a solution in the issue comments. It works for me.

Related Topics