Andorbal
commented
7 years ago Handling links is relatively easy. In history.js, you can change the third line to be:
const history = createHistory({ basename: '/50' });And all your links will work without having to change them.
Unfortunately, the bundle.js reference is /bundle.js, so if bundle.js is not in the root, the whole site will be broken. You could change line 8 of index.html to be:
<script src='/50/bundle.js'></script>While that works, I don't think changing two things is great. One thought I had would be to use an environment variable that defaulted to empty. This way, when you run npm start or npm run build you could change the expected base path to whatever you want by running BASE_PATH=/50 npm start
Another issue I noticed while messing with this is that the element doesn't show the URL to which it will go. So when you hover over the actual link, you see the existing link with a hash after it. I can replace the href attribute with the 'to' property, but that doesn't take basepath into account.
Since I don't really use different base paths, let me know how you would like it to work and we can figure something out.
findborg
I wanted to ask before I go changing anything around, Is there a way to make the base route just drop and go? For example, my test folder for this is 50 but when I click a link it goes to localhost/about... not localhost/50/about... I know how to add the 50 folder to the route. But, like I said, I was wondering if there was a way to just make it work no matter where it is placed in a folder system?