-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
Issue importing oas ruleset from @stoplight/spectral-rulesets #2240
Comments
That is weird. We fixed |
Hi @P0lip, I dont seem to have any other error logs than the one posted above (or im not sure where they would be) that shows up where the component that is utilizing the spectral should be rendered. I can fully render my component and run the above code on an example document if I dont import oas and dont add it as an extension to the custom ruleset. |
got it. Would it be possible for you to send some sample project so I can take a look at the code that gets executed? |
Nevermind, I see it now. It was re-introduced in https://github.com/stoplightio/spectral/blob/develop/packages/rulesets/src/shared/functions/index.ts |
🎉 This issue has been resolved in version @stoplight/spectral-rulesets-v1.11.2 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
Describe the bug
When trying to use the oas ruleset exported by the @stoplight/spectral-rulesets package in a backstage.io custom plugin an error occurs that does not let me render my frontend page or use the ruleset.
The error that is displayed on the webpage is:
ERROR 501: Lazy loaded chunk failed to load, try to reload the page: __importDefault is not defined
Here is how the packages are being imported:
Ive also tried importing it using "require" but get the same error when trying that way.
Here is how the packages are being used:
Environment:
Node: v1.15.1
Typescript: 4.6.4
Spectral-core: 1.13.0
Spectral-functions: 1.7.0
Spectral-parsers: 1.0.1
Spectral-ruleset-bundler: 1.3.1
Spectral-rulesets: 1.11.1
OS: MacOS Monterey
Browser: Chrome 103
The text was updated successfully, but these errors were encountered: