Skip to content
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

Build keeps looping between fetching artifacts and success and never finishes while watching #76

Closed
ranile opened this issue Oct 10, 2020 · 1 comment · Fixed by #77
Closed
Assignees
Labels
bug Something isn't working

Comments

@ranile
Copy link
Contributor

ranile commented Oct 10, 2020

Demo: video

Output for trunk config show: https://pastify-app.web.app/show/kTrK9WxqycKWU7865SlS
dist directory:
dist
Looks like the output for stylesheet is missing here.

When running build command, it finishes but the output dist directory does not contain the the css file

Steps to reproduce

I'm not entirely sure how to reproduce it but I will provide with the project that caused this issue here
In order to build this, you'll need to run rollup -c in the root of the repository after installing npm dependencies.

After encountering this issue, I tried to build this project with the branch for #69 which did not experience this issue.

@thedodd
Copy link
Member

thedodd commented Oct 10, 2020

@hamza1311 thanks for the report, turns out this is an issue with the 0.7.0 release where the finalized runtime config was not taking the canonical path of the target source HTML, which was causing a relative path to be used for the dist dir ignore instructions, which was causing changes in the dist to to not properly be ignored.

Just fixed the issue, will push a 0.7.1 release right now.

@thedodd thedodd self-assigned this Oct 10, 2020
@thedodd thedodd added the bug Something isn't working label Oct 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants