This PR is aimed at addressing the deployment issues on the main repository by updating the next.config.js file. The main changes involve removing the basePath and assetPrefix settings, which might be causing incorrect asset path resolution on GitHub Pages.
I did some research and found that basePath and assetPrefix settings are typically used for projects that are not at the root of a domain. For GitHub Pages organization sites, these settings are unnecessary and can cause issues with asset loading.
Changes Made
Removed basePath: '/capedevs.github.io' from next.config.js
Removed assetPrefix: '/capedevs.github.io/' from next.config.js
Kept other configuration settings intact
After these changes:
The site should deploy correctly on GitHub Pages
All assets (JavaScript, CSS, images) should load properly
The site should render with full styling and functionality
Testing Performed
Verified that the site loads correctly with all assets on the test deployment
Additional Notes
After merging, please trigger a new deployment to ensure the changes take effect
It may take a few minutes for the changes to propagate fully on GitHub Pages
Description
This PR is aimed at addressing the deployment issues on the main repository by updating the
next.config.jsfile. The main changes involve removing thebasePathandassetPrefixsettings, which might be causing incorrect asset path resolution on GitHub Pages.I did some research and found that
basePathandassetPrefixsettings are typically used for projects that are not at the root of a domain. For GitHub Pages organization sites, these settings are unnecessary and can cause issues with asset loading.Changes Made
basePath: '/capedevs.github.io'fromnext.config.jsassetPrefix: '/capedevs.github.io/'fromnext.config.jsAfter these changes:
Testing Performed
Additional Notes