Explore Plugin Folder Move about altv-athena HOT 6 CLOSED

Hi, nice idea that would slim framework it self, one thing i would change is aliases which can be @athena/core, @athena/server, @athena/plugins as they are more explicit.

from altv-athena.

Realistically this can be done in steps; and not all at once. Which would be adding the path aliases first. Moving all plugins to use path aliases and so on and so forth.

from altv-athena.

@gotgameio Only catch with this is that the aliases require a custom build process inside of the SWC script so I don't know how it affects your esbuild thing. I've already got a 'test' branch that made the aliases work but it would definitely force us to use one build process in general.

from altv-athena.

@Stuyk The path aliasing itself is not a problem, i already use it with esbuild/webpack in my project. I argue about @athena/ prefix because personally i use it as a library and i include athena/startup in my main resource with path alias @athena/core/server, @athena/core/client, i dont use @server/@client etc prefixes so i think as they will be used only in athena itself my build will not break, i will test 3.9.0-path-aliasing branch to check if it will break anything.

from altv-athena.

@gotgameio Okay; lemme know. Also get in Discord if you are not already in Discord.

from altv-athena.

I'm not sure if the plugin folder will be moved because of the build issues it will likely introduce. I'm still considering it but I'm not sure at this time. If anything in 4.0.0 we get the path aliasing which makes it a bit cleaner.

from altv-athena.