CC-6659: Auto build toolkit on changes

[ellacai]

🛠️ Description

Now you can do a yarn watch:toolkit which will watch for changes in toolkit/src and automatically rebuild so the documentation app will have the latest changes.
Before, you had to run yarn prepare after each toolkit change.

📸 Screenshots

video1435768332.mp4

🔗 External Links

jira

🏗️ How to Build and Test the Change

👍 Definition of Done

• New functionality works?
• Tests added?
• Docs updated?

💬 Using the Netlify feedback ladder

• 🗻 [mountain]: Blocking and requires immediate action.
• 🗿 [boulder]: Blocking.
• ⚪ [pebble]: Non-blocking, but requires future action.
• ⏳ [sand]: Non-blocking, but requires future consideration.
• ✨ [dust]: Non-blocking. "Take it or leave it"

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
consul-ui-toolkit-documentation	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 19, 2023 10:56pm

[WenInCode]

Seems to work great. Only thing that isn't working for me is if I create a new component it doesn't seem to work in the docs unless I kill it and re prepare. I am not sure what is the cause. Maybe try looking into it a bit more, but this is still a nice improvement.

[WenInCode]

might be a good idea to mention that this is using fb-watchman and maybe link to their docs.

[ellacai]

Seems to work great. Only thing that isn't working for me is if I create a new component it doesn't seem to work in the docs unless I kill it and re prepare. I am not sure what is the cause. Maybe try looking into it a bit more, but this is still a nice improvement.

hmm if you create a new component, wouldn't the documentation app throw a Attempted to resolve 'cut/new-component', which was expected to be a component, but nothing was found. error that requires a kill and re-build anyways?

maybe i'm misunderstanding but I thought that was expected ❓

[WenInCode]

@ellacai Try this flow

1. Start the documentation app
2. Add a simple component to toolkit like Cut::Fake that just renders a div with some text
3. Run yarn prepare
4. Try to use that component in documentation without restarting the build.

I'm pretty sure it will work 🤔

[ellacai]

@ellacai Try this flow

1. Start the documentation app
2. Add a simple component to toolkit like Cut::Fake that just renders a div with some text
3. Run yarn prepare
4. Try to use that component in documentation without restarting the build.

I'm pretty sure it will work 🤔

I gave it a try and I think I get the same error?
We can revisit this in a future improvement! Will merge as is for now.