Alpine.js Devtools Workflow Survey

This short 6-question survey will help me prioritise features and explore ways to make Alpine.js Devtools more sustainable.

If you use Alpine.js Devtools, I’d love your input!

(I'm collecting emails to follow up on your feedback)

Sign in to Google to save your progress. Learn more
Email *
1. How would you describe your use of Alpine.js and its Devtools? (Select the option that best matches your experience.)
 *
2. What do you use Alpine.js for? (Select all that apply) *
Required
3. Which existing DevTools features are most important to you? (Rate each on a scale of 1 to 5)
 *
1. Not important
2. Slightly important
3. Neutral
4. Important
5. Very important
1. Detect Alpine.js on a page
2. View Alpine.js components and state in devtools
3. Edit component data
4. Support for Alpine stores
5. View Alpine warnings/errors in devtools
6. Reliable state updates/sync (less need to refresh/reopen)
7. Performance on large datasets (10k properties)
8. Jump to error/component root in Elements tab
4. Which of these future improvements would benefit you the most? (Optional - Rate on a scale of 1 to 5)
1. Not valuable
2. Slightly valuable
3. Neutral
4. Valuable
5. Very Valuable
1. Active maintenance and ongoing updates
2. Modernised UI
3. State history and time travel debugging
4. Export/import state snapshots/history
5. Support for Alpine events
6. Dark mode
7. Component/property search
8. Support for `data-x-data`
9. "Production mode" which disables devtools
Clear selection
5. Would you or your company be interested in supporting the ongoing development of Alpine.js Devtools? *
6. On projects where you use Alpine.js, which other technologies do you use in conjunction with it? (Select all that apply)
7. Any other pain points, feature ideas or feedback?
Submit
Clear form
Never submit passwords through Google Forms.
This form was created inside of Code with Hugo.

Does this form look suspicious? Report

Google Forms