engine
engine copied to clipboard
wixplosives
Scalable Web Application Engine
the entire code of generating a web entrypoint (`create-entrypoint.ts` in `engine-scripts`) is a combination of template strings. This makes this peace of code to be very prone to errors and...
 to reproduce: use prepack
For example, with `yarn start:all --projectPath ../some-project --freshlyCloned`, the value of `freshlyCloned` will be undefined, not `true`. However, with `yarn start:all --freshlyCloned --projectPath ../some-project`, the value of `freshlyCloned` will be...
currently engine-scripts includes both dev-time and runtime functionality, such that its consumers are dependant on html-webpack-plugin. consider separating the runtime functionality to a separate location, s.t only the runtime functionality...
Sometimes a feature needs to define a service for its internal use. But currently there's no way to prevent other features from using it.
Currently, cross-environment service subscriptions can only be defined as `myService.subscribe(listener)` It would be really useful to also allow event name as the first argument: `myService.subscribe(event, listener)` Right now the engine...
Currently, when calling a service defined in a single-endpoint browser environment from a node environment, the engine either completes the request, or leaves it in a pending state indefinitely (if...
When starting the engine it picks up every `.config.js` file as a feature config file. E.g. when running a feature called project-picker I'm getting the following: ```sh $ engineer start...
When running `engineer --help`, descriptions of commands are missing. E.g. what the difference between `engineer start` and `engineer run`? ``` ꕤ ~/Projects/component-studio yarn engineer --help yarn run v1.22.10 $ /Users/alexeyl/Projects/component-studio/node_modules/.bin/engineer...
When trying to run a feature that is designed to work on a specific env context (`live-server`/`worker`) on another env context, it would be helpful the get a meaningful error\alert.
