linear[bot]
commented
1 year ago ENG-1014 @tinacms/cli unhandled promise errors
``` (node:31369) UnhandledPromiseRejectionWarning: Error: Unable to find collection for file at content/foundation/_index.md at TinaSchema.getCollectionByFullPath (/Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/schema-tools/dist/index.js:247:17) at Database.collectionForPath (/Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/graphql/dist/index.js:4942:25) at async Database.partitionPathsByCollection (/Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/graphql/dist/index.js:5714:26) at async /Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/graphql/dist/index.js:5590:72 at async Database.indexStatusCallbackWrapper (/Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/graphql/dist/index.js:5787:22) at async Database.indexContentByPaths (/Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/graphql/dist/index.js:5589:7) (Use `node --trace-warnings ...` to show where the warning was created) (node:31369) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:31369) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:31369) UnhandledPromiseRejectionWarning: Error: Unable to find collection for file at content/fds/_index.md at TinaSchema.getCollectionByFullPath (/Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/schema-tools/dist/index.js:247:17) at Database.collectionForPath (/Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/graphql/dist/index.js:4942:25) at async Database.partitionPathsByCollection (/Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/graphql/dist/index.js:5714:26) at async /Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/graphql/dist/index.js:5590:72 at async Database.indexStatusCallbackWrapper (/Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/graphql/dist/index.js:5787:22) at async Database.indexContentByPaths (/Users/kldavis/projects/support/ethswarm-blog-hugo/node_modules/tinacms/graphql/dist/index.js:5589:7) (node:31369) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) ``` The above error is displayed in node 14.x when running npx tinacms dev, but in later versions of node tina silently fails. The error should be caught and displayed to the user. Example repository: [https://github.com/kldavis4/ethswarm-blog-hugo](https://github.com/kldavis4/ethswarm-blog-hugo) Run npm install && npx tinacms dev using node 16.x or later and it exits immediately
vercel[bot]
CLAassistant
dependabot[bot]
Bumps @tinacms/cli from 1.5.14 to 1.5.16.
Changelog
Sourced from
@tinacms/cli's changelog.Commits
bd50b94Version Packagesfe664c2Version Packages (#3955)52b1762fix: ENG-1014: prevent unhandled promise rejection when unable to determine c...6f2a433Merge pull request #3965 from tinacms/fix-indexing-self-hostinga68781dupdate indexing message7b3cbb3update indexing messagea94bf72fix: invalid or incomplete introspection error (#3956)9f4136cIndex the content before a build when self hostingDependabot 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 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)