-
Notifications
You must be signed in to change notification settings - Fork 15
Conversation
…node directly on the changed file.
Thanks for the PR. Will take a look in the evening. In the meanwhile, could you remove commit adding |
Could we also use /src/styles as an output path instead of /src/components/styles ? This would mean changing currently imported css.js's path one folder back but would make it more acceptable for different types of packages which don't necessarily have components. |
@chanar we could change the output path, if you think it makes sense e.g. to allow utility files like |
@chanar squash / amend top commits, don't add reverts etc noise. |
@lkraav squashing is for merging two commits. Amending is for changing the commit message. |
@web-padawan I think it makes sense for encouraging adoption and using your framework packages in parallel with someone's own app. But I would wait until if you decide to merge this pull request and then make a new PR for the path changes. |
@chanar can you please comment on why |
Line 87 in 889df60
Not sure why it didn't do changes for padawan in master, to begin with. |
@lkraav it looks like I haven't run some scripts through prettier yet. The formatting changes are ok. |
This reverts commit 6728adf.
@chanar build was definitely very fast (since only the relevant component built), but there seems to be no output of what was built where (target), for clarity. Easy or not to add? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Will update and to merge into a branch first, so I could run the tests before merging to master.
@chanar legacy
Your JS globbing seems to have missed it. |
Found out that the performance issue was caused by looping through files in the bash scripts. Instead, the files from the provided path will be looped inside js.
Also, changed watch script to compile the changed file directly.