When using altiva new . in an empty directory, Altiva returns the error:

The directory '.' isn't empty.

Finish the implementation of shared libraries between components for smaller final versions.

Currently, in 2.0 branch, errors are thrown in console. As part of our effort to make Altiva modular, easily readable, usable and changeable, the modules now have to return errors to the caller, not to console.

In the CLI case, then the CLI module will show those errors in console.

Actually, the routing core of Altiva is page.js, but recently it has shown different behaviors between Firefox and Chrome when navigating with browser's buttons "back" and "forward".

• Routes
• Route groups
• Route filters

Enable Svelte's store ($) and the option to disable it in a project basis through altiva.hjson.

When a developer has sufficient information from his users behaviors, he will be able to specify which routes or components should be cached in specific situations.

Just as an example, it will be possible to determine the cache of /profile route (with all its components and subcomponents) when a user enters the /feed route.

Near real-time use for known behaviors, not just for "warmed" routes.

Currently considering pkg, but I'm open to learn the differences from other alternatives, like Nexe.

Currently, Altiva gives an altiva.auth.options property that can be used in authenticated ajax requests.

Now Qwest, that is our default bundled ajax library, create a new method qwest.setDefaultOptions, that we can use to set the JWT header permanently.

• Component creation
• Component logic
• Components in routes
• Sub-components

• Ajax
• Ajax cache

I am building a Windows 10 app with cordova but when I call the app.start( ) function from altiva,
it points to unknown location (mainfolder/components) but as the cordova build all the files are in (mainfolder/www/components). so the only thing I did to fix this problem was changing the start: function ( ) from altiva.js at:

Altiva.load.baseUrl= this.config.path + '/components/';
to:

Altiva.load.baseUrl= this.config.path + '/www/components/';

Here's my app folder:
-images
-cordova
-build
-config.xml
-www
---components
---js
---css
---(other stuffs)
---index.html
I also have tried to put components folder outside from www folder but still not working,I guess its the cordova that don't build automatically by default others paths in the app besides the default folders. So is there any other way to do this changing of path for Altiva.load.baseUrl by not altering the altiva.js?

Altiva was initially designed for specific projects.

Now it's used publicly and we hope to create a community and get contributions.

For this reason, it's indispensable to refactor all the code.

To allow developers to easily publish and use packages, a new mode must be added: altiva package [options]

This issue will track the progress of requisites to this new mode.

To be done

• altiva module install module-name
• altiva module update module-name
• altiva module remove module-name
• Complete documentation

Add options to allow generation of gzip and/or brotli files in the final build.

Allow route grouping with filters

• Route groups
• Route middlewares

• Mobile packaging

In dev mode, when adding or removing sub-components, Altiva goes into an erroneous state and only works correctly again if it is terminated and started again.

https://github.com/terkelg/tiny-glob

Work in progress...

This issue tracks the work in progress about modules in Altiva.

Since modules can be used to do things both before compilation, after it, or add functionalities in run time (browser), I will document my thoughts and ideas about the moments a module can interact (the "roles" that a module can assume). This can be a revolution in code and component sharing.

Moments of interactions / Roles

Developers can add one function or an array of functions, that will be executed in the passed order. Each role will have specific parameters that will be documented in the future.

In the case of components, instead of functions, a folder with components and (optionally) subfolders should be provided, that will be available to be used in the project.

• Before compiling: beforeCompile
• After compiling: afterCompile

• Runtime: runtime

Currently the components bse url are re-configured to mobile only with app.mobileSetup() call.

Now we can change this and always adjust the components folder, regarding of the environment.

When a different route is loaded, it's useful to provide an "onRefresh" function that could be used by the non-changing components when the route changes.

But this could also be solved by simply making the "route" variable reactive.

• Contributing
• Tools used

• How to authenticate through APIs and backends with JWT

[WIP] Working in progress

This feature allows older components to co-exist with newer ones, and selective live-on-air updates managed by the application itself.

Also, completely solves the problem of browser cache when publishing updates to the app in one or more components. The versioning strategy saves each component's version in an unique filename, which provides an unique URL.

When using something like altiva new myproject.co.uk, Altiva doesn't accept it, returning:

 You can use just letters, numbers, '-' and '_' for your project name. Or '.' to use the current directory (that must be empty).

This need to be changed since folders names with dots are perfectly fine.

Allow this:

app.route[ '/content, /content/:page' ] = {
	
	content: 'Content'
};

Replace ractive-load library with new Altiva-load module, based on rcu

Experiment and, if possible, implement selective reloading of changed files.

Make Altiva recognizes automatically in which environment it is running.

In old projects, there are cases where the altiva.hjson doesn't have all the current properties.

To solve this problem, I'm creating this issue to remember me that Altiva needs to check the user's altiva.hjson and update the missing parts, without changing the existing ones.

When the browser version is available. See lukeed/httpie#12