v1.0.0-beta.35

• fixed importPath for alem imports (Windows OS)

v1.0.0-beta.34

• Fixed file change detector

v1.0.0-beta.32

Feature: local modules files. Local modules are going to be injected only once and their references will be used throughout the app, thus reducing the final size of the final file. To add a file to be compiled as module, just add it to the src/modules folder.

Warning Points:
1 - If you want to use props inside the modules, you must pass it as a parameter. Modules live at the very top layer of Além and can't automatically access the props where it's being used.
2 - It's not recommended to add stateful components to src/modules;
3 - It supports stateless components.

• Performance improvement in the compiler;
• The way Além dependencies are loaded has been improved;
• Resource for using local modules implemented.
• It is possible to filter which files should not be interpreted as modules even if they are in the "modules" folder. Use the
  "ignoreFileIfIncludes": ["styles.ts"] inside alem.config.json.

"modules": {
    "ignoreFileIfIncludes": ["styles"]
  }

• Added heavy logic execution time logs. To enable, update your .env with SHOW_EXECUTION_TIME=true.
• Added new parsers.

v1.0.0-beta.31

4711bcf

• Types updated: OverlayTrigger, TypeAhead → Typeahead

v1.0.0-beta.30

548e8c1

• Fixed filesContentCache to allow only JavaScript and TypeScript files.

v1.0.0-beta.29

18bd484

• build CLI updated to set network value

v1.0.0-beta.28

6b7bbf5

• Added new alem.config.json options: createLoaderWidget, loadingComponentFile, loadingComponentName. These settings are used to tell the compiler whether a Widget Loader should be generated. This Loader is used to load the main Widget.

createLoaderWidget: boolean - Should the Widget Loader be created?
loadingComponentFile: string (optional) - Path to the component that will serve as loading while the main Widget content is loaded.
loadingComponentName: string (optional) - Exact name of the component being loaded via loadingComponentFile. For example, if the loading file has this structure:

const SuspenseLoading = () => <p>Loading...</p>;

So the name must be SuspenseLoading.

Config Example

"options": {
    "createLoaderWidget": true,
    "loadingComponentFile": "src/components/SuspenseLoading.tsx",
    "loadingComponentName": "SuspenseLoading"
  }

v1.0.0-beta.27

Feature: Core Improvement Beta 27

• extractSpreadsFromJSX removed. Its functionality is now part of extractPropsFromJSX;
• Added plugin (stateless_renamePropsTo__props__) to the cache system that changes any global property with name props from stateless components to __props__
  to prevent the parent widget property from being overwritten, thus correcting the conflict of
  properties that use the name props;
• Fixed the problem where when compiling Widgets, they received spreads more than once in their props.

v1.0.0-beta.26

• fixed extractJSXChildren and extractTopLevelJSXElements to support children values inside JSX elements

e.g:

<>{myItems}</>

It was previously supported only JSX elements without dynamic values inside.

e.g:

<><p>Hi</p></>

v1.0.0-beta.25

• Added support to rename prop inside a destructuring
  e.g.:

const MyComponent = ({profile: _profile}: any) => {
    console.log(_profile); // It works now as a reference to "profile"
}