engine
engine copied to clipboard
Scalable Web Application Engine
If you subscribe in a `browser` environment to a service defined in the `node` environment, and then close or reload the browser window, the unsubscribe method in `node` will never...
Service with `allowRemoteAccess` defined in an environment ENV is not accessible in an environment that depends on ENV from other features. Added a failing test: https://github.com/wixplosives/engine/commit/412f5ab403813743ceefd8ecb4301709c3864fa9 After some debugging, looks...
Project must have a webpack config, with stylable webpack plugin. This is for an app that doesn't contain React. adding stylable webpack plugin into `webpack.config.js` solves this. This is undocumented...
At the moment, if you've built a static version of an engine package, and then run `engineer start` in the same directory, the statically built version will be run. In...
* Use `react-dom/client` entry point * Update react types * Use `createRoot`
Currently if I have a monorepo, in which there are multiple features declaring the same environment (name + type), their setup calls end environment declarations get mixed up in the...
Currently we resolve requests to map requests to feature files to a global variable. We don't need this mechanism, since we already found all these paths when analyzing features.
Currently, new environment definitions by external features are not supported. New environments can be defined only in the main app features, external features are limited to use only predefined environments.
using outPath doesn't help in terms of setting the file name 
Currently the error handling in the engine, and how it is being projected to the user, doesn't help the users understand what is wrong/missing/more, and it causes frustration when using...