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

chore(deps-dev): bump @nestia/sdk from 1.6.7 to 2.3.4 #444

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Oct 23, 2023

Bumps @nestia/sdk from 1.6.7 to 2.3.4.

Release notes

Sourced from @​nestia/sdk's releases.

v2.3.4

What's Changed

Full Changelog: samchon/nestia@v2.3.3...v2.3.4

v2.3.3

What's Changed

Full Changelog: samchon/nestia@v2.3.2...v2.3.3

v2.3.2

import { INestiaConfig } from "@nestia/sdk";
import { Module, VersioningType } from "@nestjs/common";
import { NestFactory } from "@nestjs/core";
const NESTIA_CONFIG: INestiaConfig = {
input: async () => {
const app = await NestFactory.create(MyModule);
app.setGlobalPrefix("api");
app.enableVersioning({
type: VersioningType.URI,
prefix: "v",
});
return app;
},
output: "src/api",
e2e: "src/test",
swagger: {
output: "swagger.json",
security: {
bearer: {
type: "apiKey",
},
},
},
};
export default NESTIA_CONFIG;

From now on, you can configure INestApplication instance to the INestiaConfig.input property. Therefore, finally, you can utilize special features of NestJS like setGlobalPrefix(), enableVersioning(), and RouterModule.

The reason why I had not supported those features were I had not known how to get TypeScript controller files' locations in the runtime environment. In today, I could get the locations of TypeScript controller files through get-function-location library. Special thanks to @​rwjblue and his amazing strategy utilizing the inspector module.

Also, you can specify target configuration and project files by using --config [file] --project [file] options like below, instead of using nestia.config.ts and tsconfig.json files.

... (truncated)

Commits
  • 4de3179 Merge pull request #673 from samchon/features/ts5.3
  • c365281 Pending TypeScript v5.3 update.
  • 28f9192 Update dependencies of @nestia/migrate
  • 49b65d6 Merge pull request #671 from samchon/features/e2e
  • 45f01c5 Enhance e2e test functions generator
  • 4c99bfe Merge pull request #669 from samchon/features/project
  • b73d38c Complement #563: new CLI option --project.
  • 50d2d88 Publish v2.3.0
  • 292e2ef Merge pull request #668 from samchon/features/report
  • df0b006 Report errors during SDK generation.
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@nestia/sdk](https://github.com/samchon/nestia) from 1.6.7 to 2.3.4.
- [Release notes](https://github.com/samchon/nestia/releases)
- [Commits](samchon/nestia@v1.6.7...v2.3.4)

---
updated-dependencies:
- dependency-name: "@nestia/sdk"
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Oct 23, 2023
@socket-security
Copy link

New and updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives Size Publisher
@nestia/sdk 2.3.4 network, filesystem, shell +0 654 kB samchon
@nuxt/devtools 1.0.0-beta.0...1.0.0 environment +2/-3 8.54 MB antfu

@vermaysha vermaysha closed this Oct 26, 2023
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Oct 26, 2023

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/nestia/sdk-2.3.4 branch October 26, 2023 04:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant