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

issue-#97 and #98 - Fix vulnerable dependencies #99

Merged
merged 10 commits into from Jul 21, 2022
Merged

issue-#97 and #98 - Fix vulnerable dependencies #99

merged 10 commits into from Jul 21, 2022

Conversation

elycruz
Copy link
Owner

@elycruz elycruz commented Jul 20, 2022

Changes

Fixes #97, #98:

  • Updated 'ava', and 'typescript' versions.
  • Ran 'npm audit fix' to fix one critical dependency ('json-schema' dep.).
  • Added 'downleveled dts' files to the project - Helps to ensure that projects using projects *.d.ts files still work when they're typescript versions are older than typescript v4.0.
  • Added 'clean-and-build-downlevel-dts' script, for cleaning, and building, downlevel-dts files.
  • Added '.npmignore' - helps ensure that we don't upload everything in the repo when publishing the 'project' package.
  • Updated plugins 'custom' sass file importer to enforce load order.

- Updated 'ava' package version.
- Added '@ava/typescript' module to package (required by latest version of AVA).
- Updated tests to follow new syntax for 'after', and 'before, methods.
…wnlevel-dts', 'copy' steps for downlevel-dts output directory ('./ts3.5').

- Added generated 'downleveled dts' files (keeping this in the git cache
since we're already keeping the library's artifacts there - more
consistent).
… message.

- Ran auto format on 'clean-and-run' script.
@elycruz elycruz self-assigned this Jul 20, 2022
- Updated 'SassImporterResult' type to match Sass's 'LegacyImporterResult' - We had defined our type because the version of sass the library using, and sass versions users might be using, did not/may not contain this type (so basically our type was that type but slightly imprecise (we had both 'file?:...', and 'content?:...'  as part of the same interface, but actually they need to be separate ones (:-))).
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.

Is it possible to run your tests with ava 4.3.1 ?
1 participant