-
Notifications
You must be signed in to change notification settings - Fork 404
Simplify UIKit Development Experience / Workflow #1098
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
Conversation
…nc + 1st pass at wiring up the handlebars dev edition for easier UIKIt development
as we have discussed elsewhere - I am game for this but it has not been a current priority (versus clearing the PR backlog). I dont think the idea of managing our own fork of a live server if BS serves all of our needs. at the time, a contributor weighed the pros and cons and thought we should go our own way. many circumstances have changes since then |
… method to get the config PL is using
…lder to remotely compile the Handlebars demo
started reviewing this instead of #1034 - as I was seeing some similar odd behavior. more to come |
seeing this:
switching to npm? EDIT: nevermind, I figured it out.... Windows problem |
this was failing on Windows
I understand why getting hot module reloading working across all this would be beneficial. testing the PR, I get a blankscreen at localhost:3000 with no noticeable errors if I visit http://127.0.0.1:3000 instead - i see this instead this is the console output:
the symlink error I see that edit: it looks to me as if vs the edition.... another day |
Hey thanks for taking a look at this @bmuenzenmeyer! Just doing a gut check here, does it make sense what I’m trying to get to with this PR? Specifically, I want to call out the new From the UIKit folder (aka from a folder outside of where PL was installed / source files exist), I want to:
If you comment out this last line in the build tools file, what’s left in this file is basically all of the patch code to work around all the problems I kept running into several different problems:
|
Ignore Webpack entirely for a sec: I think a symptom of the problem here is that the Handlebars dev edition code isn’t compiling the HTML and data to the I believe all the UIKit errors from your screenshot are related to not having any UI or data in the served folder that UIKit is expecting to find... I can totally adjust paths from the UIKit side of things if need be — really could use your help figuring out why getting PL’s Node API to compile and watch for changes (if your current directory isn’t the same folder as your source files) is so finicky + the Windows aliasing issues... 🤪 |
Yes I think conceptually this should be possible. Turns out it's a good
gut check of this theory!
I'll have more time later this week
…On Wed, Nov 20, 2019, 6:46 AM Salem Ghoweri ***@***.***> wrote:
it looks to me as if www does not have everything it may need. i wonder if
build/webpack-server` needs path.sep work too
Ignore Webpack entirely for a sec: I think a symptom of the problem here
is that the Handlebars dev edition code isn’t compiling the HTML and data
to the www temp folder when run from outside of the
packages/development-edition-engine-handlebars folder.
I believe all the UIKit errors from your screenshot are related to not
having any UI or data in the served folder that UIKit is expecting to
find...
I can totally adjust paths from the UIKit side of things if need be —
really could use your help figuring out why getting PL’s Node API to
compile and watch for changes (if your current directory isn’t the same
folder as your source files) is so finicky + the Windows aliasing issues...
🤪
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1098?email_source=notifications&email_token=AACI3Q4WZ536T2GMM4RQXI3QUUWQRA5CNFSM4JNOSCV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEER3MSA#issuecomment-555988552>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACI3Q4GHV4B5547ZDNPUE3QUUWQRANCNFSM4JNOSCVQ>
.
|
Updated with a much simpler config required + wired up the |
this works outstanding! made a simple sass change in the uikit and it showed up in the running development edition HUZZAH! |
@sghoweri gonna play with that this weekend, thanks! |
@sghoweri Just letting you know I was able to follow the instructions and have things working. Thanks a ton for this! |
@bradfrost awesome, glad to hear it!! Just keep in mind that while the UI is largely refactored at this point, there’s still at least a few things on my radar to clean up. Namely:
Looking forward to what you come up with! |
Ship it!
…On Sat, Nov 23, 2019, 1:03 PM Brad Frost ***@***.***> wrote:
@sghoweri <https://github.com/sghoweri> Just letting you know I was able
to follow the instructions and have things working. Thanks a ton for this!
[image: Screen Shot 2019-11-23 at 2 02 58 PM]
<https://user-images.githubusercontent.com/383701/69483813-fd8b3d00-0df9-11ea-8b1a-21feeb8328e0.png>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1098?email_source=notifications&email_token=AACI3QYSYE5S7OI4A6JOKU3QVF47NA5CNFSM4JNOSCV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE73RCA#issuecomment-557824136>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACI3Q7DTAR7DYOXLOYFLJTQVF47NANCNFSM4JNOSCVQ>
.
|
…-uikit-dx RFC: Simplify UIKit Development Experience / Workflow
1st pass at making Pattern Lab's UIKit development process a bit more streamlined and repeatable for awesome folks like @bradfrost.
There's still definitely some kinks I'm still working out with the CLI (especially when exiting out of the watch task — might need to hit theGetting up and running for local UIKit development should be as simple as running the following:control
+c
keys twice grumble grumble) but with these updates,