Lock file maintenance all dependencies (non-major) #28

renovate · 2021-06-13T18:40:07Z

This PR contains the following updates:

Package	Type	Update	Change
		lockFileMaintenance	All locks refreshed
@prisma/client (source)	dependencies	minor	All locks refreshed
@railway/cli	devDependencies	patch	All locks refreshed
@slack/bolt (source)	dependencies	minor	All locks refreshed
@slack/web-api (source)	dependencies	minor	All locks refreshed
prisma (source)	devDependencies	minor	All locks refreshed
ts-node (source)	dependencies	minor	All locks refreshed
typescript (source)	dependencies	minor	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

Release Notes

prisma/prisma

`v2.30.3`

Compare Source

Today, we are issuing the 2.30.3 patch release.

Improvements

Prisma CLI

Adapt CLI update notifier for major upgrade #9061

Fixes

Prisma Studio

npx prisma studio throws spawn undefined\System32\WindowsPowerShell\v1.0\powershell ENOENT error on windows

`v2.30.2`

Today, we are issuing the 2.30.2 patch release.

Fixes

Prisma Client

A NOT within a NOT creates a SQL query with only a single NOT in 2.30.0

`v2.30.0`

Compare Source

Today, we are excited to share the 2.30.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

New features & improvements

Full-Text Search for PostgreSQL is now in Preview 🚀

We're excited to announce that Prisma Client now has preview support for Full-Text Search on PostgreSQL.

You can give this a whirl in 2.30.0 by enabling the fullTextSearch preview flag:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["fullTextSearch"]
}

model Post {
  id     Int    @&#8203;id @&#8203;default(autoincrement())
  title  String @&#8203;unique
  body   String
  status Status
}

enum Status {
  Draft
  Published
}

After you regenerate your client, you'll see a new search field on your String fields that you can query on. Here are a few examples:

// returns all posts that contain the words cat *or* dog.
const result = await prisma.post.findMany({
  where: {
    body: {
      search: 'cat | dog',
    },
  },
})

// All drafts that contain the words cat *and* dog.
const result = await prisma.posts.findMany({
  where: {
    status: "Draft",
    body: {
      search: 'cat & dog',
    },
  },
})

You can learn more about how the query format works in our documentation. We would love to know your feedback! If you have any comments or run into any problems we're available in this in this Github issue.

Validation errors for referential action cycles on Microsoft SQL Server ℹ

Microsoft SQL Server has validation rules for your schema migrations that reject schema changes that introduce referential action cycles.
These scenarios tend to show up often for developers using the referentialActions preview feature, which will become the default. The database error you get is not really helpful, so to provide a better experience, Prisma now checks for referential cycle actions when it validates your schema file and shows you the exact location of the cycle in your schema.

To learn more, check out the documentation.

`prisma introspect` is being deprecated in favor of `prisma db pull` 👋🏻

The prisma introspect command is an alias for prisma db pull so they are the same command. However, prisma db pull is more intuitive since it pulls the schema from the database into your local schema.prisma file. This naming also works as the counterpart of prisma db push.

Starting with this release, you will get a warning that encourages you to use prisma db pull instead of prisma introspect.

Prisma Adopts Semantic Versioning (SemVer)

As previously announced, we are adjusting our release policy to adhere more strictly to Semantic Versioning.

In the future, breaking changes in the stable development surface i.e. General Availability will only be rolled out with major version increments.

You can learn more about the change in the announcement blog post.

Fixes and improvements

Prisma Client

Prisma Migrate

Language tools (e.g. VS Code)

@prisma/engines npm package

Cannot find namespace 'debug' in 2.29.0

Credits

Huge thanks to @saintmalik for helping!

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, August 26 at 5pm Berlin | 8am San Francisco.

`v2.29.1`

Compare Source

Today, we are issuing the 2.29.1 patch release.

Fixes

Prisma Client

`v2.29.0`

Compare Source

Today, we are excited to share the 2.29.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Major improvements & new features

Interactive Transactions are now in Preview

Today we’re introducing Interactive Transactions – one of our most debated feature requests.

Interactive Transactions are a double-edged sword. While they allow you to ignore a class of errors that could otherwise occur with concurrent database access, they impose constraints on performance and scalability.

While we believe there are better alternative approaches, we certainly want to ensure people who absolutely need them have the option available.

You can opt-in to Interactive Transactions by setting the interactiveTransactions preview feature in your Prisma Schema:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["interactiveTransactions"]
}

Note that the interactive transactions API does not support controlling isolation levels or locking for now.

You can find out more about implementing use cases with transactions in the docs, and share your feedback.

Named Constraints are now in Preview

Named Constraints allow you to represent (when using introspection) and specify (when using Prisma Migrate) the names of constraints of the underlying database schema in your Prisma schema.

Before this release, you could only specify the underlying database constraint names for @@unique and @@index. This meant that you didn't have control over all constraint names in the database schema. In projects that adopted Prisma with introspection, some constraint names from the database were not represented in the Prisma schema. This could lead to the database schema across environments getting out of sync when one environment was introspected, and another was created with Prisma Migrate and had different constraint names.

Starting with this release, you can specify the underlying database constraint names for @id, @@id, @unique, and @relation constraints.

You can opt-in to Named Constraints by adding the namedConstraints preview feature to your Prisma Schema:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["namedConstraints"]
}

After enabling the namedConstraints preview flag, you can specify the names of constraints in the database schema using the map attribute:

@id(map: "custom_primary_key_constraint_name")
@@id([field1, field2], map: "custom_compound_primary_key_name")
@unique(map: "custom_unique_constraint_name")
@@unique([field1, field2], map: "custom_compound_unique_constraint_name")
@@index([field1, field2], map: "custom_index_name")
@relation(fields: [fieldId], references: [id], map: "custom_foreign_key_name")

After specifying the map attribute, Prisma Migrate will use it when creating migrations.

When using prisma db pull with namedConstraints, these names will be automatically populated in your Prisma schema unless they match our default naming convention (which follows the Postgres convention). When handwriting a Prisma schema, these names are optional and will alternatively be filled with the default names by Prisma under the hood.

The `name` argument in `@@unique` and `@@id`

In addition to the map argument, the @@unique and the @@id attributes have the name argument (optional) that Prisma uses to generate the WhereUnique argument in the Prisma Client API.

Note: You can use both name and map together, e.g. @@unique([firstName, lastName], name: "NameOfWhereUniqueArg", map: "NameOfUniqueConstraintInDB")

For example, given the following model:

model User {
  firstName String
  lastName  String

  @&#8203;@&#8203;id([firstName, lastName])
}

The following Prisma Client query is valid:

const user = await prisma.user.findUnique({
  where: {
    // firstName_lastName is the default `name`
    firstName_lastName: {
      firstName: 'Ada',
      lastName: 'Lovelace',
    },
  },
})

By adding the name argument to the @@id attribute:

model User {
  firstName String
  lastName  String

-  @&#8203;@&#8203;id([firstName, lastName])
+  @&#8203;@&#8203;id([firstName, lastName], name: "fullname")
}

The following query is valid:

const user = await prisma.user.findUnique({
  where: {
    // fullname comes from the name argument
    fullname: {
      firstName: 'Ada',
      lastName: 'Lovelace',
    },
  },
})

Note: For the @@unique attribute this functionality was already available in previous releases. For @@id this is new.

You can learn more about namedConstraints in our documentation.

Please check our upgrade guide before enabling the preview flag and running migrate operations for the first time. It explains what to do if you either want to keep the existing names in your database or want to switch to the default names for a cleaner Prisma schema.

Prisma Adopts Semantic Versioning (SemVer)

As previously announced, we are adjusting our release policy to adhere more strictly to Semantic Versioning.

In the future, breaking changes in the stable development surface i.e. General Availability will only be rolled out with major version increments.

You can learn more about the change in the announcement blog post.

Fixes and improvements

Prisma Client

Prisma Migrate

Credits

Huge thanks to @benkenawell for helping!

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, March 04 at 5pm Berlin | 8am San Francisco.

`v2.28.0`

Compare Source

Today, we are excited to share the 2.28.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟

MongoDB improvements 🚀

Thanks to your feedback, we fixed a handful of bugs reported on the MongoDB connector (Preview):

Concurrent findUnique queries leading to an error #8276
Filtering by relations wasn't working properly #7057
Filtering on an array of IDs #6998

Please keep reporting issues to our team and help to bring MongoDB support closer to GA!

Prisma Adopts Semantic Versioning (SemVer)

We are adjusting our release policy to adhere more strictly to Semantic Versioning.

In the future, breaking changes in the stable development surface i.e. General Availability will only be rolled out with major version increments.

You can learn more about the change in the announcement blog post.

Create new Prisma projects in under 3 minutes ⏳

The latest release of the Prisma Data Platform enables you to create new Prisma projects and provision a database in under 3 minutes.

The Prisma Data Platform already allows you to:

Explore data in the database using the data browser.
Add other users to it, such as your teammates or your clients.
Assign users one of four roles: Admin, Developer, Collaborator, Viewer.
View and edit your data collaboratively online.

The new onboarding flow makes it possible to get started with Prisma quickly for new Prisma projects! 🚀

When creating a new Prisma project, the Prisma Data Platform allows you to:

Choose a Prisma schema from a selection of our templates.
Create a free PostgreSQL database on Heroku.
Populate the database with seed data.

If you already have a Prisma project, you can continue to import it from GitHub and connect it to your database.

This whole process now takes less than 3 minutes to set up, so we’re looking forward to seeing how you will use this feature for your prototyping and production needs.

If you have any issues or questions, let us know by opening a GitHub issue.

Quick overview

If you have a Heroku account, we can create a free Postgres database for you:

Start your project with a schema from our templates:

Interested in Prisma’s upcoming Data Proxy for serverless backends? Get notified! 👀

Database connection management in serverless backends is challenging: taming the number of database connections, additional query latencies for setting up connections, etc.

At Prisma, we are working on a Prisma Data Proxy that makes integrating traditional relational and NoSQL databases in serverless Prisma-backed applications a breeze. If you are interested, you can sign up to get notified of our upcoming Early Access Program here:

https://pris.ly/prisma-data-proxy

Fixes and improvements

Prisma Client

Prisma Migrate

Using render.com database for migrate dev leads to error message ERROR: cannot drop view pg_buffercache because extension pg_buffercache requires it HINT: You can drop extension pg_buffercache instead.

Prisma Studio

Credits

Huge thanks to @ShubhankarKG, @hehex9 for helping!

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, July 15 at 5pm Berlin | 8am San Francisco.

`v2.27.0`

Compare Source

Today, we are excited to share the 2.27.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟

Major improvements & new features

MongoDB is Now in Preview 🎉

We're thrilled to announce that Prisma now has Preview support for MongoDB. Here's how to get started:

Inside your schema.prisma file, you'll need to set the database provider to mongodb. You'll also need to add mongoDb to the previewFeatures property in the generator block:

// Set the database provider to "mongodb"
datasource db {
  provider = "mongodb"
  url      = env("DATABASE_URL")
}

// We want to generate a Prisma Client
// Since mongodb is a preview feature, we need to enable it.
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["mongoDb"]
}

// Create our Post model which will be mapped to a collection in the database.
// All posts have a required `title`, `slug` and `body` fields.
// The id attributes tell Prisma it's a primary key and to generate 
// object ids by default when inserting posts.
model Post {
  id    String @&#8203;id @&#8203;default(dbgenerated()) @&#8203;map("_id") @&#8203;db.ObjectId
  slug  String @&#8203;unique
  title String
  body  String
}

Next, you'll need to add a database connection string to your .env file. We recommend using MongoDB Atlas to spin up a MongoDB database for free. Set the DATABASE_URL to the connection string you got from MongoDB Atlas, it should be similar to the following string:

DATABASE_URL="mongodb+srv://admin:<password>@&#8203;cluster0.quvqo.mongodb.net/myFirstDatabase?retryWrites=true&w=majority"

❗️ Don't forget to include the username and password you set while creating the database in the connection string, otherwise you won't be able to connect to it.

Then you can run npx prisma generate to generate a MongoDB-compatible Prisma Client. The Prisma Client API is the same for Mongo as it is for other supported relational databases (PostgreSQL, MySQL, SQLite and Microsoft SQL Server).

To test that everything works, you can run the following script:

import { PrismaClient } from "@&#8203;prisma/client"
const prisma = new PrismaClient()

async function main() {
  // Create the first post
  await prisma.post.create({
    data: {
      title: "Prisma <3 MongoDB",
      slug: "prisma-loves-mongodb",
      body: "This is my first post. Isn't MongoDB + Prisma awesome?!",
    },
  })
  // Log our posts showing nested structures
  console.dir(posts, { depth: Infinity })
}

main()
  .catch(console.error)
  .finally(() => prisma.$disconnect())

You should see a new post created and added to your database! You can use Prisma Studio to view the record you just added by running npx prisma studio.

This is just the tip of the iceberg. Learn more in our Getting Started Guide.

We would love to know your feedback! If you have any comments or run into any problems we're available in this issue. You can also browse existing issues that have the MongoDB label.

Prisma native support for M1 Macs 🚀

This one's for our Mac users. Prisma now runs natively on the new M1 chips. Best of all, there's nothing to configure, it just works. Enjoy the speed bump!

Fixes and improvements

Prisma Client

Prisma Migrate

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, July 15 at 5pm Berlin | 8am San Francisco.

`v2.26.0`

Compare Source

Today, we are excited to share the 2.26.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Major improvements & new features

Referential Actions now enable cascading deletes and updates (Preview)

In this release we are introducing a new feature in Preview which enables fine-grained control over referential actions ON DELETE and ON UPDATE for the foreign keys supporting relations in Prisma models.

Current behavior

Until now, Prisma created a foreign key for each relation between Prisma models with the following defaults: ON DELETE CASCADE ON UPDATE CASCADE. In addition, when invoking the delete() or deleteAll() methods, Prisma Client performs runtime checks and will prevent the deletion of records on required relations if there are related objects referencing it, effectively preventing the cascade delete behavior. When using raw SQL queries for deletion, Prisma Client won't perform any checks, and deleting a referenced object will effectively cause the deletion of the referencing objects.

Example:

model User {
  id    String @&#8203;id
  posts Post[]
}

model Post {
  id       String @&#8203;id
  authorId String
  author   User   @&#8203;relation(fields: [authorId])
}

prisma.user.delete(...) and prisma.user.deleteAll() will fail if the user has posts.

Using raw SQL, e.g. using $queryRaw() to delete the user will trigger the deletion of its posts.

New behavior

⚠️ Turning on this feature could, when using delete() and deleteMany() operations, delete more data than before under certain circumstances. Make sure you read down below to understand why and anticipate these changes.

The feature can be enabled by setting the preview feature flag referentialActions in the generator block of Prisma Client in your Prisma schema file:

generator client {
  provider = "prisma-client-js"
  previewFeatures = ["referentialActions"]
}

With the feature enabled, the behavior is now the following:

It's possible to choose specific referential actions for the foreign keys in relations. Prisma Migrate, prisma db push, and introspection will set these in the database schema, e.g. @relation(... onDelete: SetNull) will set translate to ON DELETE SET NULL on the corresponding foreign key. See Syntax section below.
When the onDelete or onUpdate attributes in @relation are not present, default values are used:
- ON DELETE RESTRICT (NO ACTION on SQL Server) for required relations
- ON DELETE SET NULL for optional relations
- ON UPDATE CASCADE for all relations regardless if optional or required.
Prisma Migrate, prisma db push, and introspection will rely on the syntax and default values above to keep the referential actions between Prisma schema and database schema in sync.
Prisma Client no longer performs any checks before deleting records when invoking delete() or deleteAll() methods. Deleting referenced objects will succeed or not depending on the underlying foreign keys of relations, e.g. by default deletion will be prevented by the database because it's set to ON DELETE RESTRICT, but will succeed if set to ON DELETE CASCADE.
Upgrade path: If developers don't specify custom onDelete or onUpdate attributes in the Prisma schema, the next time the database is updated with Prisma Migrate or prisma db push, the database schema will be updated to use the default values on all foreign keys, ON DELETE RESTRICT ON UPDATE CASCADE (ON DELETE NO ACTION ON UPDATE CASCADE on SQL Server).
Please note that until then, if the database schema is managed using Prisma Migrate or prisma db push, the existing defaults are probably in place (ON DELETE CASCADE ON UPDATE CASCADE), and this could lead to deletion of records in conditions where a deletion was previously prevented by Prisma Client until the foreign key constraints are updated.

Syntax

The semantics of onDelete and onUpdate are almost exactly how SQL expresses ON UPDATE and ON DELETE. For the example below:

If the related author (User) of a Post is deleted (onDelete), delete all Post rows that are referencing the deleted User (Cascade).
If the id field of the related User is updated, also update authorId of all Posts that reference that User.

model User {
  id    String @&#8203;id
  posts Post[]
}

model Post {
  id       String @&#8203;id
  authorId String
  author   User   @&#8203;relation(fields: [authorId], onDelete: Cascade, onUpdate: Cascade)
}

Possible keywords for onDelete and onUpdate are: Cascade, Restrict (except SQL Server), NoAction, SetNull, SetDefault.

If you run into any questions or have any feedback, we're available in this issue.

Limitations

Certain combinations of referential actions and required/optional relations are incompatible. Example: Using SetNull on a required relation will lead to database errors when deleting referenced records because the non-nullable constraint would be violated.
Referential actions can not be specified on relations in implicit many-to-many relations. This limitation can be worked around by switching to explicit many-to-many relations and specifying the referential actions on the relations in the relations table.

`prisma init` now accepts a `--datasource-provider` argument

The prisma init command now accepts a --datasource-provider argument that lets you configure the default provider for the initially generated datasource block in your Prisma schema. The possible values for this argument are equivalent to the allowed values for the provider field on datasource blocks:

postgresql (default)
mysql
sqlite
sqlserver (Preview, needs the microsoftSqlServer preview feature flag)

Here's an example that shows how to configure the initial Prisma schema skeleton with a SQLite database:

npx prisma init --datasource-provider sqlite

Node-API Improvements

The Prisma Client currently communicates to Prisma's Query Engine over either HTTP or Unix domain sockets. After some experimentation, we realized we can improve this communication overhead by using Node-API, which provides direct memory access across processes.

We've been working the last couple of weeks to get ready to make Node-API the default way we communicate with the Query Engine. To prepare for this change, we fixed a bunch of bugs and we'd love for you to give it another try:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["nApi"]
}

Right now we're still compiling benchmarks, but you should see a nice speed boost by opting into Node-API. You can reach us in this issue if you run into anything!

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma

Credits

Huge thanks to @B2o5T for helping!

🌎 Prisma Day is happening today!

Prisma Day is a two-day event of talks and workshops by members of the Prisma community, on modern application development and databases. It's taking place June 29-30th and is entirely online.

June 29th: Workshops
June 30th: Talks

We look forward to seeing you there!

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, July 01 at 5pm Berlin | 8am San Francisco.

railwayapp/cli

`v0.2.43`

Compare Source

Changelog

e7d4be7 CLI now returns latest updated projects (#151)

`v0.2.42`

Compare Source

Changelog

e7d4be7 CLI now returns latest updated projects (#151)

`v0.2.41`

Compare Source

Changelog

259d5c4 Support --environment for Up + Fix Exit Status' (#150)

`v0.2.40`

Compare Source

Changelog

93b774d Support Environment flag for run (#148)

`v0.2.39`

Compare Source

Changelog

25879db enable default non-dynamic completions (#146)
6a8b23f Use updated variable methods (#145)

`v0.2.38`

Compare Source

Changelog

688ebc7 fetch all starter templates (#147 )

slackapi/bolt

`v3.6.0`

Compare Source

Added Slack Connect Events (#999, #1008) - Thanks @srajiang
Made App start() account for AWSLambdaReceiver return type (#1038, #1039) - Thanks @seratch
Added tests for SocketModeReciver (#750, #1021) - Thanks @filmaj
Docs, docs, docs and example app improvements! (#1062, #1066, #1067, #1059 , #1046, #1056, #1048, #1039, #1023, #939, #1021, #1033) - Thanks @sisisin, @hariNEzuMI928, @RhnSharma and @stevengill, @seratch, @filmaj, @srajiang

`v3.5.0`

Compare Source

Added support for FileInstallationStore (#941, #1003) - Thanks, @misscoded!
Fix to existing code snippet around acknowledging events (#997) - Thanks, @Zimboboys!
Brought Socket Mode to the forefront of the Getting Started docs (#990) - Thanks, @srajiang!
Documentation updates and improvements (#989, #1002) - Thanks, @srajiang and @misscoded!

`v3.4.1`

Compare Source

Updated default axios options to include proxy:false to match @slack/web-api package (#979) - thanks @stevengill
Fixed AwsLambdaReceiver failing to parse event.body if isBase64Encoded is true (#971, #972) - thanks @TheManWhoStaresAtCode
Added edited property to app_mention event payload (#960, #961) - thanks @seratch and @hi-se
Added a new deploy-aws-lambda project to the examples directory (#815, #940) - thanks @TheManWhoStaresAtCode
Use Kanji for Japanese documents (#983) - thanks @disneyresidents

slackapi/node-slack-sdk

`v6.4.0`

Compare Source

Added Sign in With Slack (OpenID Connect) support (#1296, #1307) - Thanks @seratch
Add Slack Connect APIs response types and tests (#1284, #1283, #1306) - Thanks, @srajiang and @seratch
Adding "private" property in shares in files API responses (#1294, #1303) - Thanks, @seratch and @JeanBarriere.
Added more info to rate limited error exception message (#1214, #1312) - Thanks @seratch
Updated admin.users.invite endpoint (#1297, #1298) - Thanks @stevengill!

`v6.3.0`

Compare Source

Add Slack Connect (conversations.*) and admin.auth.policy.* support (#1283, #1284) - Thanks, @srajiang!
Updated Web API response types (#1285) - Thanks, @seratch!
Added Node 16.x to the CI (#1249) - Thanks, @connorads!
Fixed the PinsAddArguments and PinsRemoveArguments interfaces (#1277) - Thanks, @rr-codes!
Added support for Axios timeout customization (#1264) - Thanks, @misscoded!

TypeStrong/ts-node

`v10.2.1`

Compare Source

Fixed

Fixes #1426: Do not import typescript outside of configuration/project loading (#1433, #1426) @Songkeys
- We take care to load your project's version of typescript, falling back to a globally-installed version if necessary.
- 10.2.0 introduced a bug where we did not do this consistently, causing global or npx installations of ts-node to attempt loading typescript relative to themselves, not your project.
- This failed if typescript was not globally installed or npx did not install peer dependencies.

https://github.com/TypeStrong/ts-node/milestone/6

`v10.2.0`

Compare Source

Questions about this release? Ask in the official discussion thread: #1423

Added

Adds top-level await support to REPL (#1383, #245) @ejose19
- can be disabled with --no-experimental-repl-await, experimentalReplAwait, or TS_NODE_EXPERIMENTAL_REPL_AWAIT (CLI docs, API docs)
Setting "pretty": false disables pretty formatting of diagnostics even when stdout is a TTY (#1418, #1420) @elevatebart
- Applies to ts-node's pretty option, not to be confused with TypeScript's pretty option
Ignores diagnostics which are annoying in an interactive REPL (#1396, #1120, #729, #850, #469)
- For example, when you input const foo = 1 in the REPL, foo is unused. We ignore the resulting diagnostic foo is declared but its value is never read
- Diagnostics are only ignored in the REPL
- Diagnostics for non-REPL files imported by the REPL will still be shown
Logged stack traces are colorized to match vanilla node's behavior (#1412, #1405)

Fixed

Fix #1397: SWC transpiler should emit ECMAScript imports and exports when configuration dictates (#1409, #1397)
- Enables SWC transpiler to be used alongside --loader
Fix #1403: source-map-support breaks rendering of node errors (#1405, #1403)
Fix #1410: rendering of async stack frames should include async annotations (#1405, #1410)
Fix [#1

Configuration

📅 Schedule: "before 5am on monday" in timezone Asia/Kolkata.

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

renovate bot added the renovate label Jun 13, 2021

renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 3 times, most recently from 14f2b97 to 032cafb Compare June 17, 2021 20:20

renovate bot changed the title ~~Lock file maintenance all dependencies (non-major)~~ Lock file maintenance Jun 18, 2021

renovate bot force-pushed the renovate/all-dependencies-(non-major) branch from 032cafb to 924b70e Compare June 18, 2021 21:44

renovate bot force-pushed the renovate/all-dependencies-(non-major) branch from 924b70e to 86251f2 Compare August 2, 2021 11:37

renovate bot changed the title ~~Lock file maintenance~~ Lock file maintenance all dependencies (non-major) Aug 2, 2021

renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 3 times, most recently from eb9aff5 to f03fdce Compare August 10, 2021 16:31

renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 3 times, most recently from 36408f2 to 2ce90d0 Compare August 19, 2021 19:09

renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 4 times, most recently from f6650fa to 5acc69c Compare August 30, 2021 16:56

Lock file maintenance all dependencies (non-major)

353525a

renovate bot force-pushed the renovate/all-dependencies-(non-major) branch from 5acc69c to 353525a Compare September 2, 2021 16:50

khrj closed this May 7, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Lock file maintenance all dependencies (non-major) #28

Lock file maintenance all dependencies (non-major) #28

renovate bot commented Jun 13, 2021 •

edited

Loading

Lock file maintenance all dependencies (non-major) #28

Lock file maintenance all dependencies (non-major) #28

Conversation

renovate bot commented Jun 13, 2021 • edited Loading

Release Notes

Improvements

Prisma CLI

Fixes

Prisma Studio

Fixes

Prisma Client

New features & improvements

Full-Text Search for PostgreSQL is now in Preview 🚀

Validation errors for referential action cycles on Microsoft SQL Server ℹ

prisma introspect is being deprecated in favor of prisma db pull 👋🏻

Prisma Adopts Semantic Versioning (SemVer)

Fixes and improvements

Prisma Client

Prisma Migrate

Language tools (e.g. VS Code)

@​prisma/engines npm package

Credits

📺 Join us for another "What's new in Prisma" livestream

Fixes

Prisma Client

Major improvements & new features

Interactive Transactions are now in Preview

Named Constraints are now in Preview

The name argument in @@&#8203;unique and @@&#8203;id

Prisma Adopts Semantic Versioning (SemVer)

Fixes and improvements

Prisma Client

Prisma Migrate

Credits

📺 Join us for another "What's new in Prisma" livestream

MongoDB improvements 🚀

Prisma Adopts Semantic Versioning (SemVer)

Create new Prisma projects in under 3 minutes ⏳

Quick overview

Interested in Prisma’s upcoming Data Proxy for serverless backends? Get notified! 👀

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma Studio

Credits

📺 Join us for another "What's new in Prisma" livestream

Major improvements & new features

MongoDB is Now in Preview 🎉

Prisma native support for M1 Macs 🚀

Fixes and improvements

Prisma Client

Prisma Migrate

📺 Join us for another "What's new in Prisma" livestream

Major improvements & new features

Referential Actions now enable cascading deletes and updates (Preview)

Current behavior

New behavior

Syntax

Limitations

prisma init now accepts a --datasource-provider argument

Node-API Improvements

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma

Credits

🌎 Prisma Day is happening today!

📺 Join us for another "What's new in Prisma" livestream

Changelog

Changelog

Changelog

Changelog

Changelog

Changelog

Configuration

renovate bot commented Jun 13, 2021 •

edited

Loading

`prisma introspect` is being deprecated in favor of `prisma db pull` 👋🏻

@prisma/engines npm package

The `name` argument in `@@unique` and `@@id`

`prisma init` now accepts a `--datasource-provider` argument