Skip to content
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

fix: handle scenario where declaration file has code file as self #246

Merged
merged 2 commits into from
Jan 10, 2023

Conversation

dsherret
Copy link
Member

@dsherret dsherret commented Jan 9, 2023

Closes #230

@dsherret dsherret changed the title fix: handle scenario where declaration file has no corresponding code file fix: handle scenario where declaration file has code file as self Jan 10, 2023
@dsherret dsherret marked this pull request as ready for review January 10, 2023 16:50
@dsherret dsherret merged commit b1bb08e into main Jan 10, 2023
@dsherret dsherret deleted the fix_handle_scenario_declaration_no_code_file branch January 10, 2023 16:53
cowboyd added a commit to thefrontside/platformscript that referenced this pull request Feb 9, 2023
We upgrade to use the `yaml` package and not the `yaml-ast-parser`
package. However, we needed to pin the build at a particular version
which apparently caused problems with older versions of DNT.

However, this has been fixed with
denoland/dnt#246

This upgrades the NPM build to use the latest version of DNT, and it
also runs the NPM build as part of the branch verification. That way,
if the NPM build breaks in the future, we'll know about it immediately.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for pinned esm.sh modules?
1 participant