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
{{ message }}
This repository has been archived by the owner on Aug 14, 2021. It is now read-only.
Various process.env references made its way in the bundle in the last release, for example when including a package via CDN and its esm bundle. we need to make sure, that all env references get replaced during build and afterwards we have to verify that said include works. So for core-components for example, this served html code (located in root of core-components):
We still need to build a test to validate this works, cypress still has a few open issues in order to check for uncaught promise exceptions so I can't test the above yet but as soon as its possible we need the cypress tests to validate the bundle
It would just be to build each plugin and then use the above html snippet to call the appropriate entry point esm.js and in cypress we just need to boot and visit that page and check there is no uncaught promises thrown & that we can see the sample "hello" corejam-box rendered that should be enough to validate it on a high level
Although saying that, i havent checked the latest cypress release yet so the issues may actually be solved so we can do that now. ill take a look again
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Various
process.env
references made its way in the bundle in the last release, for example when including a package via CDN and its esm bundle. we need to make sure, that all env references get replaced during build and afterwards we have to verify that said include works. So for core-components for example, this served html code (located in root of core-components):should not throw a js error.
The text was updated successfully, but these errors were encountered: