appblocks-hub / bb-cli Goto Github PK

I would like to request a feature that allows for custom endpoint names in addition to the current practice of using the block name as the endpoint name. This would provide us with greater flexibility to change our endpoint names as needed.

Even though I chose single build while trying to build the backend, it's not working. It's still running the normal build. It's taking too much time.

I would like to request to include the tailwind config and related config files that we have created in Elements. Currently, when running applications, these files are not included in the emulator.

I request to combine webpack.config rules and configuration for each block element.
Currently, we are manually refactoring the generateWebpackConfig.js file to achieve this.

Error in creating ui element

ui element not starting
giving error starting ui element

Error on admin_fe_signups: Unexpected string in JSON at position 1730

missing , in devDependencies

https://github.com/appblocks-hub/BB-CLI/blame/c4363f20cb7d029034199a9983f2a6872e5f3a70/templates/createTemplates/uiElement-templates/generate-packageJson.js#L63

Feature request

What is the expected behavior?
CLI should automatically restart the app when any change is made into the code.

What is the current behavior?
user need to manually run bb stop and bb start <app_name> to see changes in effect

When deploying a project using bb deploy -env Production and choosing a function block as the target, the shared functions are not getting packaged or used.

And even after deploying a function that doesn't require any shared function, the ALB link is not returning anything

But the AWS ECS cluster seems to be running healthy

Deploying a project using a GitHub action pipeline seems to be far away
These are the steps missing currently

1. Authenticating bb-cli on a headless environment
2. Pulling all the blocks mentioned in block.config.json into the pipeline runtime using a single command
3. Running bb upload with arguments. currently, it only supports an interactive approach. same for bb deploy
4. Running build commands for blocks that require a build like ui-container in a centralized approach. (Low priority)

Currently, it takes hours of effort to deploy a project and the chances of making an error are very high

JSON request body is returning undefined as the emulator created by CLI doesn't have the JSON parsing middleware enabled.
Please add support by adding JSON middleware

Issue description

could not load env file inside the standalone app folder.The env files which is in container folder (.env.functions & .env.view) can be accessed but only with providing a full relative path in 'dotenv' configuration

Steps to reproduce the issue

1.1. create a .env file inside the standalone app folder
1.2. try to access it with 'dotenv' like const env = dotenv.config({ path:'.env' }) //undefined
2.1 try with .env.functions or .env.view like const env = dotenv.config({ path:'.env.functions' }) //undefined
2.2. try again with providing relative path like const env = dotenv.config({ path:'../.env.functions' }) //works

What's the expected result?

• env should be loaded easily without providing full relative path either from the standalone app folder or from the container app