The extensions.js file throws an error when i try to run an extension

[AbegaM]

Describe the bug

I am trying to run a soul extension inside the soul/core folder but the code is throwing an error in the /core/src/extensions.js file, i have followed the instructions in here to run the extension.

To Reproduce

1. Go to the soul/core folder and create a folder named _extensions

2. Create a file named api.js inside the _extensions folder and copy and paste the sample extension code from here

3. Add the path of your extension in your .env file

   EXTENSIONS=./_extensions
   

4. Run the project

   npm run dev
   

Expected behavior
When i run the project, it throws an error in this line, it can't require the _extensions/api.js file,

Screenshots

Additional context
The code works fine when i modify the path of the extension like this

- const apiExtensions = require(`${extensionsPath}/${extension}`);

+ const apiExtensions = require(`../${extensionsPath}/${extension}`);

[thevahidal]

Hi @AbegaM,
you should provide the "absolute" path.
e.g. EXTENSIONS=/home/user/soul/core/_extensions

[thevahidal]

Just updated the https://github.com/thevahidal/soul/blob/main/docs/extensions-examples.md to mention the importance of absolute paths for the extensions directory.

[AbegaM]

@thevahidal Thank you so much for your answer. I just changed it to an absolute path and everything is working fine now.

[IanMayo]

Hello @thevahidal - is there a strong technical reason why the path has to be absolute?

It can make deployment of a Soul-based solution more challenging - including the fact that extensions will not work "out of the box" on a clone of the repo (since we can't forecast the directory structure above the repo).

[thevahidal]

Hey @IanMayo,
No there's not a strong reason behind it, it was just easier as Soul is basically a CLI.
But I can change it so it supports relative paths from where you run the CLI.

[thevahidal]

Hey @IanMayo, No there's not a strong reason behind it, it was just easier as Soul is basically a CLI. But I can change it so it supports relative paths from where you run the CLI.

Issue created.
#78