add integration tests for dev/prod#4446
Merged
yaacovCR merged 1 commit intographql:nextfrom Jul 5, 2025
Merged
Conversation
yaacovCR
force-pushed
the
integration
branch
3 times, most recently
from
4dea05f to
85a8c4a
Compare
extracted from graphql#4437
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this pull request
Jul 30, 2025
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from graphql#4437
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this pull request
Dec 17, 2025
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from graphql#4437
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this pull request
Dec 17, 2025
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from graphql#4437
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this pull request
Dec 17, 2025
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from graphql#4437
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this pull request
Dec 18, 2025
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from graphql#4437
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this pull request
Dec 19, 2025
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from graphql#4437
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this pull request
Dec 22, 2025
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from graphql#4437
yaacovCR
added a commit
that referenced
this pull request
Dec 22, 2025
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from #4437
yaacovCR
added a commit
that referenced
this pull request
Dec 22, 2025
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from #4437
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this pull request
Jan 27, 2026
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from graphql#4437
yaacovCR
added a commit
that referenced
this pull request
Feb 22, 2026
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from #4437
yaacovCR
added a commit
that referenced
this pull request
Feb 23, 2026
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from #4437
yaacovCR
added a commit
that referenced
this pull request
Feb 24, 2026
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from #4437
yaacovCR
added a commit
that referenced
this pull request
Feb 24, 2026
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from #4437
yaacovCR
added a commit
that referenced
this pull request
Feb 24, 2026
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from #4437
yaacovCR
added a commit
that referenced
this pull request
Feb 24, 2026
currently, the only difference between development and production modes is the behavior of the instanceOf() check "production" mode is currently enabled by setting `process.env.NODE_ENV` to `production` with the default mode being "development" mode. this PR demonstrates how to enable production mode with node, bun, deno, esbuild, rollup, swc, webpack, and rspack and demonstrates the default of development mode in those environments as well as with jest and vitest. extracted from #4437
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
currently, the only difference between development and production modes is the behavior of the
instanceOf()checkextracted from #4437