-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parcel build not working #43
Comments
My guess is Ex: dist/article/0.html will look for navigation.html as './navigation.html' when it should be looking at '../navigation.html'. I couldn't find ways for parcel to fix this. One workaround is to just write a script that fixes the paths in child directories:
You can automate this by adding In articles.ejs, works.ejs, replace the navigation header element with the code in navigation.ejs and replace the header-id from "top-container" to "nav-styling". Copy the code in navigation.scss to the bottom of init.scss, renaming "top-container" to "nav-styling". This is not the ideal solution, so leaving this open until someone finds the right way to use parcel to resolve it. |
I just removed parcel from this project. Thank you for reporting. |
Running 'npm run build' results in a few errors in the compressed files. Namely, the html files in /dist result in "ERR_FILE_NOT_FOUND" as they try to find each other.
It looks like "parcel build" has an issue with relative assets: parcel-bundler/parcel#206
A partial solution is, on line 44 in tools/build.sh, add: "--public-url ./"
But the files in articles and work still have the relative path error. Not sure how others haven't run into this issue.
The text was updated successfully, but these errors were encountered: