You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are having an interesting discussion at DefinitelyTyped/DefinitelyTyped#67290. Essentially, we realized with kriasoft/node-sqlite#177 that there are some legit use cases where the sqlite3 typings are needed but it's not desirable to pull in the entire sqlite3 npm package.
It looks like @types/sqlite3 has fallen into disuse, but I was curious what everyone thought of keeping the typings there since the sqlite3 interface has become something of a de-facto standard.
Proposed implementation
Move typings back to @types/sqlite3
The text was updated successfully, but these errors were encountered:
Summary
We are having an interesting discussion at DefinitelyTyped/DefinitelyTyped#67290. Essentially, we realized with kriasoft/node-sqlite#177 that there are some legit use cases where the sqlite3 typings are needed but it's not desirable to pull in the entire sqlite3 npm package.
It looks like @types/sqlite3 has fallen into disuse, but I was curious what everyone thought of keeping the typings there since the sqlite3 interface has become something of a de-facto standard.
Proposed implementation
Move typings back to @types/sqlite3
The text was updated successfully, but these errors were encountered: