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
fix(cli,build): dev warnings default on for undeclared extensions, scanner edge fixes
Inverts the extension-declaration default: an extension that declares no
installed packages is assumed to install none, so dev warnings stay live
for third-party and yet-to-declare extensions instead of silently
disabling the feature (proven twice by first-party sweeps missing
extensions). The incomplete guard remains only where false warnings are
genuinely likely: a throwing declaration hook, or an additionalPackages
extension too old to declare, and the engine-only prisma mode now
declares @prisma/engines. Also: specifier-form exports (export { req })
are followed cross-file, npm-alias install tokens suppress the aliased
name, literal Windows path specifiers never warn, the bare-specifier
check reuses isBareModuleImport, collector usages swap atomically per
build, exported-name mention checks use identifier boundaries, and
signature-miss re-reads run under the concurrency cap with failures
logged.
Copy file name to clipboardExpand all lines: .changeset/warn-createrequire-deploy.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,4 +4,4 @@
4
4
"@trigger.dev/core": patch
5
5
---
6
6
7
-
`deploy` and `dev` now warn, with the file, line, and suggested `additionalPackages` fix, when code loads a package through `createRequire()` that won't be available in the deployed image and would previously only fail at runtime in production.
7
+
`deploy` and `dev` now warn, with the file, line, and suggested `additionalPackages` fix, when code loads a package through `createRequire()` that won't be available in the deployed image and would previously only fail at runtime in production. Deploys also now show the bundler's own warnings for your code instead of discarding them.
0 commit comments