You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read and understand the suggestion guidelines
Checked for duplicate suggestions
I checked for existing similar suggestions
Summary
Hi,
We're working on a new addon framework that supports SDK V2, and I was wondering if it was possible for us to check that the addon supports advanced minify at build time (as in, at least causes no crashes) to make it easier to develop addons that work for it since this is a very common issue.
Ideally, I'd just wanna know what tools you use for minifying and what settings you use, and how you decide failure. That way I could add that to the framework and give a warning or throw an error at build time to help addon devs make addons
Possible workarounds or alternatives
Keep doing what we do atm, aka manually test for it. I suppose that I could in theory write a Puppeteer script that installs the addon in C3 and exports a blank project but that seems a bit overkill and would make build times a lot LOT longer which I don't want.
Proposed solution
Get more info, or tools that would help us implement this.
Why is this idea important?
It's not absolutely important, I just think it would be a cool addition to the framwork
Additional remarks
No response
The text was updated successfully, but these errors were encountered:
Reviewed guidelines
Checked for duplicate suggestions
Summary
Hi,
We're working on a new addon framework that supports SDK V2, and I was wondering if it was possible for us to check that the addon supports advanced minify at build time (as in, at least causes no crashes) to make it easier to develop addons that work for it since this is a very common issue.
ConstructFund/construct-addon-wizard-scaffold#18
Ideally, I'd just wanna know what tools you use for minifying and what settings you use, and how you decide failure. That way I could add that to the framework and give a warning or throw an error at build time to help addon devs make addons
Possible workarounds or alternatives
Keep doing what we do atm, aka manually test for it. I suppose that I could in theory write a Puppeteer script that installs the addon in C3 and exports a blank project but that seems a bit overkill and would make build times a lot LOT longer which I don't want.
Proposed solution
Get more info, or tools that would help us implement this.
Why is this idea important?
It's not absolutely important, I just think it would be a cool addition to the framwork
Additional remarks
No response
The text was updated successfully, but these errors were encountered: