You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I would like to thank you for this great project! ✌️
If the path to the current working directory contains a hidden directory (e.g. .fractal-workspace), the build process will not find the fractal components and the static export will not correct generated.
Steps to reproduce the issue
Create a new hidden directory, e.g. in your user home directory. mkdir -p .fractal-workspace/main && cd .fractal-workspace/main
Create Fractal project skeleton ./node_modules/.bin/fractal new test-project
Answer all questions with yes (hit Enter)
Set builder destination path in config cd test-project/ && echo "fractal.web.set('builder.dest', path.join(__dirname, 'build'));" >> fractal.config.js
Run Fractal build-process NODE_ENV=debug ./node_modules/.bin/fractal build
Current result
The example component of the skeleton project isn't generated in the /build folder and also not referenced in the exported html files (e.g. index.html).
Only 6 items to be exported are found, but there must be 9.
⚑ Finished parsing components directory
⚑ Finished parsing docs directory
✔ Build started...
⚑ Exported '/' ==> '/index.html'
⚑ Exported 1 of 6 items
⚑ Exported 2 of 6 items
⚑ Exported 3 of 6 items
⚑ Exported 5 of 6 items
⚑ Exported 6 of 6 items
⚑ Copied '/Users/ms/.fractal-workspace/main/test-project/node_modules/@frctl/mandelbrot/dist' ==> '/Users/ms/.fractal-workspace/main/test-project/build/themes/mandelbrot'
✔ Build finished with no errors.
Expected result
If the path to the current working directory does not contain a hidden directory, the build process will run as expected and the example component will be generated.
You can just rename the folder for testing: cd ../../../ && mv .fractal-workspace fractal-workspace && cd fractal-workspace/main/test-project
And run the build again: NODE_ENV=debug ./node_modules/.bin/fractal build
⚑ Finished parsing docs directory
⚑ Finished parsing components directory
✔ Build started...
⚑ Exported '/assets' ==> '/assets.html'
⚑ Exported 1 of 9 items
⚑ Exported 2 of 9 items
⚑ Exported 3 of 9 items
⚑ Exported 5 of 9 items
⚑ Copied '/Users/ms/fractal-workspace/main/test-project/public' ==> '/Users/ms/fractal-workspace/main/test-project/build'
⚑ Exported 6 of 9 items
⚑ Exported 7 of 9 items
⚑ Exported 9 of 9 items
⚑ Copied '/Users/ms/fractal-workspace/main/test-project/node_modules/@frctl/mandelbrot/dist' ==> '/Users/ms/fractal-workspace/main/test-project/build/themes/mandelbrot'
✔ Build finished with no errors.
Reproduces how often:
Always
Context
Fractal version: 1.5.11
Node version: v16.8.0
OS: macOS 12.0.1 and Debian 11
The text was updated successfully, but these errors were encountered:
Hello fractal devs! I hope you are well.
It would be great if you could have a look at this deviant behavior or possibly give a brief initial assessment as far as possible.
Thanks in advance!
Hey, thanks for the report. I haven't had a chance to investigate or analyze this yet and quite frankly cannot promise when I can do so. I do remember something similar from the past, but did not manage to find it as of yet.
Can you maybe help prioritize this a bit - how important is the fix, can you use a workaround etc?
It is not that urgent and i have already implemented a temporary workaround.
However, since it took me a few hours to figure out why the Fractal build process runs successfully, but no components are generated during the deployment, I thought it couldn't hurt to ask again. Also in the hope that others will be spared this in the future.
The workaround is, that i copied the normal GitLab Runner for projects with Fractal Integration and adjusted the configurations so that the build process is not executed in a hidden directory.
However, this means that changes to the runner- or deployment-configuration always have to be made in two places.
So this is not the optimal long-term solution, but it works for now.
First of all, I would like to thank you for this great project! ✌️
If the path to the current working directory contains a hidden directory (e.g.
.fractal-workspace
), the build process will not find the fractal components and the static export will not correct generated.Steps to reproduce the issue
mkdir -p .fractal-workspace/main && cd .fractal-workspace/main
npm init -y && npm install --save @frctl/fractal
./node_modules/.bin/fractal new test-project
Answer all questions with yes (hit Enter)
cd test-project/ && echo "fractal.web.set('builder.dest', path.join(__dirname, 'build'));" >> fractal.config.js
NODE_ENV=debug ./node_modules/.bin/fractal build
Current result
example
component of the skeleton project isn't generated in the/build
folder and also not referenced in the exported html files (e.g. index.html).Expected result
example
component will be generated.cd ../../../ && mv .fractal-workspace fractal-workspace && cd fractal-workspace/main/test-project
NODE_ENV=debug ./node_modules/.bin/fractal build
Reproduces how often:
Always
Context
The text was updated successfully, but these errors were encountered: