Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

esm import cjs in third-party-package will get exports.default instead of module.exports #1719

Closed
lisonge opened this issue Oct 27, 2021 · 2 comments · Fixed by #1849
Closed

Comments

@lisonge
Copy link

lisonge commented Oct 27, 2021

npm init -y
npm i esbuild node-html-parser typescript
npx tsc --init
echo 'import { parse, HTMLElement } from "node-html-parser";console.log({ parse, HTMLElement });' > test.ts
npx esbuild test.ts --bundle --outfile=test.js
node test.js

will be output

{ parse:undefined, HTMLElement:undefined }

example https://github.com/lisonge/test-cli/runs/3958824691?check_suite_focus=true#step:10:1

probable cause taoqf/node-html-parser#166 (comment)

I can also delete exports in package.json to solve it, but that is not convenient,

Is there any other solution?

@evanw
Copy link
Owner

evanw commented Oct 28, 2021

You have stumbled into an unfortunate interoperability mess. It happens when an ES module imports a CommonJS module with the default property present and the __esModule property set to true. Different tools just do different things for historical reasons, so basically you should just avoid ever doing this to maximize compatibility. The node-html-parser does this when node-html-parser/esm/index.js imports the default import from node-html-parser/dist/index.js, which causes this problem.

Background

Here's the historical context (at least from what I understand, although I could be wrong):

When ES modules first appeared, everyone used Babel to compile them to CommonJS so they could be evaluated. When converting ESM exports, all export names became properties on exports and then the special __esModule flag was set to true to indicate that the resulting CommonJS module used to be an ES module. When converting ESM imports, all import statements became a require() call and then if the special __esModule flag was set on the object returned by require(), the named ESM imports were matched up with properties on that object. So if you had both a default export and a default import in the original ESM code, everything would work fine.

Then node later came out with a way to import CommonJS from ESM, except they made it work differently. This caused all of these compatibility problems. The default import was always the value of the exports object no matter what. So when importing from a CommonJS module that was compiled from an ES module, you have to access default.default to get the original default export in node but just default to get the original default export in Babel. This mess could have been avoided if node had just followed the existing CommonJS-from-ESM semantics instead of doing something different, but I believe the problem was that the __esModule property is a run-time thing while ESM export names are a compile-time thing. Although ironically node is now statically analyzing CommonJS to generate ESM export names after all, so this actually would have been possible. Anyway that ship has sailed.

There are both a ton of old packages that were published to npm containing ES modules that expect to be evaluated the Babel way (since everyone used to have to compile with Babel before running ES modules), and also new packages being published to npm containing ES modules that expect to be evaluated the node way (since now you can just run ES modules in node without translation). Tools like esbuild, webpack, parcel, rollup, etc. need to decide if a given ES module is supposed to be run one way or the other way, and if they get it wrong either old packages break or new packages break. Each tool probably uses slightly different heuristics to try to guess which way to go. The heuristic currently used by esbuild is that the default export is the exports object (like node) except when exports.__esModule && 'default' in exports is true, in which case the default export is exports.default (like Babel).

Incompatibilities

Here is an example of the differences between tools. As you can see, esbuild currently matches rollup's behavior but otherwise every tool does something different:

webpack parcel esbuild rollup
import { parse } from "node-html-parser" function parse() function parse() undefined undefined
import x from "node-html-parser" { parse: function parse() } function parse() function parse() function parse()

I can try to tweak esbuild's heuristics here although that will likely break someone else's package. A reasonable approach would probably be to try to replicate Webpack's behavior for this as much as possible since it's the most widely-used bundler. AFAIK they run in node-mode with the .mjs extension or with "type": "module" and otherwise run in Babel-mode. I'm not sure if they take into account "exports": { "import": {} } as is the case here or not. This would need more investigation.

How to fix this

There isn't a trivial way for you to deal with this on your own, since the presence of exports prevents you from directly importing the relevant files. You can bypass this with an esbuild plugin that intercepts the import of node-html-parser and resolves it to node-html-parser/dist/index.js. Here's an example esbuild plugin:

let fixNodeHtmlParserPlugin = {
  name: 'fix-node-html-parser',
  setup(build) {
    build.onResolve({ filter: /^node-html-parser$/ }, () => {
      return { path: require.resolve('node-html-parser') }
    })
  },
}

The author of the node-html-parser package could also fix this interoperability issue themselves by changing their code to avoid exporting default in the ESM source files that are then compiled to CommonJS files by TypeScript. But it sounds like they don't want to do this. So the interoperability issue with node-html-parser will likely persist.

There's a big discussion about this over at #532 for even more context.

lachlancollins added a commit to TanStack/query that referenced this issue May 29, 2023
I can't believe these issues still exist, see evanw/esbuild#1719
TkDodo added a commit to TanStack/query that referenced this issue Jul 24, 2023
* release: v5.0.0-alpha.11

* refactor(core): unify hydration options (#5131)

* refactor: unify hydration options

* docs: update hydration docs

* migration guide

* refactor: use shouldDehydrate... syntax

* Update docs/react/guides/migrating-to-v5.md

Co-authored-by: Fredrik Höglund <[email protected]>

* Apply suggestions from code review

* chore: fix tests

* chore: fix tests

* Update docs/react/reference/hydration.md

---------

Co-authored-by: Fredrik Höglund <[email protected]>

* release: v5.0.0-alpha.12

* release: v5.0.0-alpha.13

* chore: remove unused devDependencies (#5211)

* refactor(react-query-devtools): move devtools components in files (#5150)

* refactor(react-query-devtools): move QueryStatusCount header to subdirectory

* refactor(react-query-devtools): move QueryRow to subdirectory

* refactor(react-query-devtools): move ActiveQuery to subdirectory

* refactor(react-query-devtools): move Cache Panel to subdirectory

* lint

* refactor: add display names

* fix: typo

* release: v5.0.0-alpha.14

* fix(solid-query): SSR fixes - Inconsistent state (#5093)

* fix(solid-query): do not call unsubscribe on the server

* fix(solid-query): prefer val from queryResource if

it is available there

* chore: add hydration debugger to solid ssr example

* bump minimum solid-js version

* chore: pnpm i

* chore: fix rollup babel typings

Result of this change upstream that types the “targets” property -> https://github.com/DefinitelyTyped/DefinitelyTyped/pull/63927/files#diff-a4da813bfdc10bbb7d4d9ee9b811309e7e2a16c0484b9a334752db84be4b0f31

Signed-off-by: marbemac <[email protected]>

* replace void 0

Signed-off-by: marbemac <[email protected]>

* chore: remove uncessary onMount

Signed-off-by: marbemac <[email protected]>

* chore: skip this onComputed on first render

Signed-off-by: marbemac <[email protected]>

* fix: copy state properties over for ssr hydration

Signed-off-by: marbemac <[email protected]>

---------

Signed-off-by: marbemac <[email protected]>

* release: v5.0.0-alpha.15

* fix(solid-query): Fix non hydrating queries (#5229)

* release: v5.0.0-alpha.16

* release: v5.0.0-alpha.17

* docs(react): fix typo in TypeScript.md (#5239)

Signed-off-by: Eng Zer Jun <[email protected]>

* fix: do not mutate input (#5240)

* fix: do not mutate input

params passed to function from consumers should be treated as readonly and thus shouldn't be modified

* test: remove unexpected `exact` props from find methods

---------

Co-authored-by: Damian Osipiuk <[email protected]>

* release: v5.0.0-alpha.18

* docs: update migrating-to-v5 (#5274)

I think the rocket emoji is causing a visual bug too but since I edited this through GitHub's UI, I couldn't confirm.

* fix(query-core): correct placeholderData prevData value with select fn (#5227)

* fix(query-core): correct placeholderData prevData

* fix(query-core): preserves correct prevQueryResult

This commit preserves the correct previous result between rerenders.

* test(react-query): Test with placeholder & select

* fix(query-core): Add lastDefinedQueryData property

* fix(query-core): Remove console.log

* fix(query-core): Add react-query test

* release: v5.0.0-alpha.19

* feat(solid-query): Add `reconcile` option (#5287)

* feat(solid-query): Add `reconcile` option

* feat(solid-query): Add `reconcile` callback test

* release: v5.0.0-alpha.20

* chore: adapt tests to v5 syntax after merge

* feat: remove callbacks from QueryObserver (#5282)

* feat: remove callbacks from QueryObserver

types are passing now

* test: remove some more callback related tests

* docs: migration guide for removed callbacks

* chore: fix broken lock file

* chore: remove unused variables

those were only needed on main for keepPreviousData, which doesn't exist anymore

* release: v5.0.0-alpha.21

* fix(solid-query): Remove unserializable values (#5326)

* release: v5.0.0-alpha.22

* feat: rename throwErrors to throwOnError (#5318)

* feat: rename throwErrors to throwOnError

to be aligned with the options we already have on imperative methods, like `invalidateQueries`

* docs: fix outdated code reference

* chore: rename type

* fix: let the refetchInterval function also return undefined

and fall back to false if it does

* release: v5.0.0-alpha.23

* docs: remove duplicated `isInitialLoading` (#5327)

* fix: make sure codemods are included in react-query (#5340)

* chore: fix pr pipeline (#5345)

* chore: remove unneeded script

* chore: fix syntax error after merging

* Empty-Commit

* chore: update to node18 to hopefully fix CI issues

see: vitest-dev/vitest#1191 (comment)

* chore: don't throw error if build dir already exists

* release: v5.0.0-alpha.24

* feat: queryOptions helper function (#5153)

* feat: queryOptions helper function

so that we can define and share options outside of useQuery, but still get the type inference

* docs: queryOptions

* docs: remove reference to onError

* docs: update migration guide

* release: v5.0.0-alpha.25

* chore: remove createStore option (#5352)

having the option to customize the internal store sound nice, but the problem is that the store holds Query instances, not data. So, the setter is only called once, not on every data update. This makes it relatively useless - every time we thought we could leverage createStore, it fell short of our requirements because of this.

The better way is usually to subscribe to the QueryCache directly

* docs: remove callbacks from useQuery

* fix(core): make sure refetching multiple queries imperatively works offline (#5249)

* fix(core): make sure refetching multiple queries imperatively works offline

* test: add another test for different networkMode

* fix: always catch promises even if we don't return them because we are offline

* release: v5.0.0-alpha.26

* chore: svelte-query tests, validatePackages changes

* feat(devtools): Add framework agnostic devtools (#5347)

* feat(devtools): Add framework agnostic devtools draft

* Fix test

* Move query-devtools build before react-query-devtools

* Fix dimensions bug & add isInitialOpen props

* Fix isOpen state

* Add devtools cutom errorTypes option

* Add explicit close button

* Add keyboard focus for tooltips

* Add query-core to query-devtools peerDependencies

* Update pnpm lock file

* Add overflow hidden to hide filters on top view

* Revert overflow hidden - causing other issues

* Update documentation

* Fix validate-packages script

---------

Co-authored-by: Dominik Dorfmeister <[email protected]>

* fix(query-devtools): Add query-core to devDependencies (#5360)

* fix(query-devtools): Add query-core to devDependencies

* Fix pnpm-lock.yaml

* release: v5.0.0-alpha.27

* feat(solid-query): `queryOptions` helper for solid-query (#5355)

* feat: queryOptions helper for solid-query

* add tests

* fix imports

* release: v5.0.0-alpha.28

* feat(svelte-query-devtools): Svelte Adapter for new Devtools (#5362)

* Implement working devtools component

* Fix pnpm-lock.yaml

* Update workspace config

* Always a prettier error

* Fix eslint error

* Fix test:types

* Add svelte-query to deps

* Use esm-env to block loading in prod

* Remove example changes

* Simpler export

* Allow dynamically editing props

* Run prettier

* fix(devtools): Update ESM export extension (#5364)

* fix(devtools): Update ESM export extension

* Update Svelte devtools types error

* Fix svelte-query-devtools types error

* release: v5.0.0-alpha.29

* feat(devtools): Make queryclient reactive (#5366)

* release: v5.0.0-alpha.30

* Revert changes to svelte-query build

* fix(svelte-query-devtools): Fix tsconfig paths

* fix(svelte-query-devtools): Fix issue parsing JSX (#5372)

* feat(query-core): Add previousQuery to placeholderFn (#5358)

* feat(query-core): Add previousQuery to placeholderFn

* Add query-core and react-query tests

* Remove unused query type

---------

Co-authored-by: Dominik Dorfmeister <[email protected]>

* release: v5.0.0-alpha.31

* docs: Update dependent-queries.md (#5391)

I believe `isLoading` has been renamed to `isPending`

* refactor: unwrap listeners

* chore: relax eslint for tests

* release: v5.0.0-alpha.32

* docs: new docs for placeholderData

* feat(useQueries): combine (#5219)

* attempt at adding combine on observer level (doesn't work)

* feat(useQueries): combine

adapt getOptimisticResult to return both the result array and a combined result getter

* feat(useQueries): combine

make sure combinedResult stays in sync with result

* feat(vue-query): combine results for useQueries hook

* Add new options to svelte-query

* Add new options to solid-query

* fix: enable property tracking for useQueries

* fix: move property tracking to react layer

* chore: remove logging

* chore: remove unnecessary type assertion

* test: tests for combined data

* docs: combine

---------

Co-authored-by: Damian Osipiuk <[email protected]>
Co-authored-by: Lachlan Collins <[email protected]>
Co-authored-by: Aryan Deora <[email protected]>

* docs: combine

* chore: setup fallback base to origin/main

if we trigger a release manually via github, this value might not be filled

* release: v5.0.0-alpha.34

* docs: update installation

* chore: Improve eslint/tsconfig setup in svelte packages (#5438)

* fix(types): fix TError generic on queryOptions

* release: v5.0.0-alpha.35

* release: v5.0.0-alpha.36

* chore: Bump eslint version to 8.34.0 (#5439)

* feat(svelte-query): Simplify types (#5442)

* release: v5.0.0-alpha.37

* chore: Update dev dependencies (#5466)

* chore: Replace cp with cpy-cli (#5441)

Co-authored-by: Dominik Dorfmeister <[email protected]>

* fix: Update typescript-eslint (#5467)

* release: v5.0.0-alpha.38

* chore: More package updates (#5468)

* chore: Link examples to workspace packages (#5469)

* feat(svelte-query): Switch to moduleResolution bundler (#5471)

* fix: Downgrade chalk to v4 (#5472)

* release: v5.0.0-alpha.39

* docs: change Hydrate->HydrationBoundary (#5455)

* updated docs on SSR
Hydrate -> HydrationBoundary

* docs(ssr): change Hydrate->HydrationBoundary

change Hydrate->HydrationBoundary to remove deprecated component

* docs(ssr): rename all Hydrate->HydrationBoundary

rename all Hydrate instances ->HydrationBoundary for consistency

* feat(react-query-persist-client): await onuccess (#5473)

* fix: have `onSuccess` return a promise too so that we can await it

that way, invalidation or mutations that run in onSuccess will still keep isRestoring to be false, which avoids race conditions

* test: test for awaiting onSuccess

* docs: onSuccess

* release: v5.0.0-alpha.40

* release: v5.0.0-alpha.41

* chore: Regenerate alpha lockfile (#5477)

* docs(solid-query): Fix API signature in overview.md (#5470)

* docs(svelte-query): Add svelte-query-devtools to examples (#5478)

* chore: Clean-up eslint config (#5481)

* chore: More eslint improvements (#5482)

* feat: Convert rollup config to ESM (#5484)

* chore: Migrate scripts to ESM (#5486)

* feat: Split rollup config for Nx caching (#5487)

* fix: Fix CJS/ESM issue with @commitlint/parse

I can't believe these issues still exist, see evanw/esbuild#1719

* chore: Update prettier, eslint, rollup, scripts (#5490)

* chore: Fix prettierignore

* release: v5.0.0-alpha.42

* fix: Update @commitlint/parse (#5491)

See conventional-changelog/commitlint#3614

* release: v5.0.0-alpha.43

* chore: Add eslint-plugin-compat (#5495)

* Fix workspace links

* Add eslint-plugin-compat

* Update nx.json

* fix: Improve workspace tsconfig (#5497)

* release: v5.0.0-alpha.44

* fix: Move deps/devDeps/peerDeps to appropriate location (#5498)

* chore: Extend base tsconfig for svelte packages (#5501)

* release: v5.0.0-alpha.45

* chore: Make test:types have no Nx output (#5500)

* feat: Remove svelte field from package.json (#5504)

* release: v5.0.0-alpha.46

* feat: Add explicit package.json `type` field (#5505)

* release: v5.0.0-alpha.47

* chore: Fix nx affected (#5509)

* fix: Fix ESLint warnings (#5510)

* release: v5.0.0-alpha.48

* chore: Update to Nx 16.3.1 (#5514)

* chore: Update to nx 16.3.1

* Update pnpm-lock.yaml

* chore: Update Nx cloud workflow (#5515)

* feat: Drop legacy webpack v4 support (#5507)

* release: v5.0.0-alpha.49

* feat: Remove UMD build output (#5517)

* release: v5.0.0-alpha.50

* chore: Rework rollup externals (#5519)

* feat: Refactor package exports (#5520)

* chore: Remove publint error temporarily

* release: v5.0.0-alpha.51

* fix: Publint error in solid-query (#5522)

* release: v5.0.0-alpha.52

* fix: Simplify exports in solidjs packages (#5523)

* release: v5.0.0-alpha.53

* chore: Improve Nx task separation (#5524)

* Fix ci workflow

nx run-many doesn't use --base

* feat(query-devtools): Lazyload Query Devtools Core (#5527)

* release: v5.0.0-alpha.54

* fix(query-devtools): Broken package.json exports (#5528)

* Make publint throw errors

* Rewrite CJS files to use .cjs extension

* Add concurrency option to PR workflow

* Fix export extensions

* release: v5.0.0-alpha.55

* chore: Re-enable Nx Distributed Task Execution (#5518)

* fix(query-devtools): inform onlineManager when offline mode is simulated (#5534)

* release: v5.0.0-alpha.56

* docs: make returning a promise for optimistic updates more explicit (#5485)

* fix(codemod): do not mark the `buildMessage` method as private (#5546)

* fix(codemod): do not mark the `buildMessage` method as private

It might fail because of the lack of support.

* chore(codemod): add missing `filePath` parameter to the docblock

* release: v5.0.0-alpha.57

* fix(query-devtools): Fix getSidedProp bug (#5551)

* release: v5.0.0-alpha.58

* chore: Update publish script (#5559)

* fix(query-devtools): Add chunkFileNames option (#5560)

* release: v5.0.0-alpha.59

* fix: Change `svelte-package` output directory (#5561)

* release: v5.0.0-alpha.60

* release: v5.0.0-alpha.61

* chore: try to stabilize test

* fix(solid-query): Use rollup-preset-solid (#5565)

* release: v5.0.0-alpha.62

* feat: Add legacy rollup builds (#5570)

* release: v5.0.0-alpha.63

* docs: Add `"private": true` to examples (#5578)

* release: v5.0.0-alpha.64

* fix(useIsMutating): fix vue warning (#5453)

onScopeDispose() is called when there is no active effect scope to be associated with

* release: v5.0.0-alpha.65

* feat(infiniteQuery): allow prefetching arbitrary amounts of pages (#5440)

* refactor: combine fetching first page with refetching

as it's the same condition

* feat(infiniteQuery): allow prefetching arbitrary amounts of pages

* test prefetching

* fix: make sure that pages and getNextPageParam are passed in tandem to (pre)fetchInfiniteQuery

* docs: prefetching

* chore: try to stabilize test

* docs: migration guide

* release: v5.0.0-alpha.66

* refactor: move queryOptions to its own file (#5480)

* refactor: remove 'use client' from non-components

* refactor: move queryOptions to its own file

where we don't have a 'use client' directive, because we can call this function on the server as well

* Revert "refactor: remove 'use client' from non-components"

This reverts commit 8ecac66.

* refactor: rename isRestoring file

* chore: fix import

* release: v5.0.0-alpha.67

* fix: Update eslint-plugin-query build config (#5601)

* fix: Use pnpm workspace protocol (#5600)

* release: v5.0.0-alpha.68

* chore: Use nx watch command (#5605)

* fix(solid-query): revert package.json typo (#5615)

* release: v5.0.0-alpha.69

* release: v5.0.0-alpha.70

* release: v5.0.0-alpha.71

* chore: Fix Nx parallelisation for vue-query tests (#5635)

Co-authored-by: Dominik Dorfmeister <[email protected]>

* fix(devtools): padding for action buttons (#5608)

global `button` styles would otherwise affect buttons

* release: v5.0.0-alpha.72

* feat: Support Svelte v4 (#5659)

* feat: Support svelte v4

* Downgrade @testing-library/svelte

* Upgrade @testing-library/svelte to 4.0.3

* Refactor onMount dynamic import

* release: v5.0.0-alpha.73

* fix(eslint-plugin-query): Use tsup to generate types (#5666)

* release: v5.0.0-alpha.74

* fix: Skip queryClient context lookup if client passed directly (#5669)

* release: v5.0.0-alpha.75

* feat: Accept all svelte stores as options (#5672)

* refactor: Accept stores other than writable

* Cleanup Readable type import

* Add tests

* Stricter isSvelteStore check

* Update docs

* Fix input bind

* Add testing-library cleanup

* release: v5.0.0-alpha.76

* fix(svelte-query): Fix staleTime reactivity bug (#5682)

* release: v5.0.0-alpha.77

* chore(svelte-query): Update reactivity docs and tests (#5683)

* fix(query-devtools): Bundle all dependencies (#5684)

* release: v5.0.0-alpha.78

* release: v5.0.0-alpha.79

* feat: react-query-next-experimental package (#5598)

* chore: fix a copy-paste error

* chore: bootstrap package

* chore: setup package

* chore: allow passing with no tests

* fix: remove 'use client' from index bundle

* chore: cleanup copy/paste error

* chore: fix prettier

* refactor: replace ref with direct props access

* fix: do not write to refs during render

* refactor: inline function into useEffect to avoid useCallback

* fix: eslint no-shadow

* refactor: namespace id

* refactor: removed pointless check

* fix: set to empty array on cleanup

* fix: adapt for v5 changes

* chore: fix build

* docs: add streaming example

* chore: fix outdated lockfile

* chore: fix prettier

* refactor: remove isSubscribed ref

* refactor: re-arrange comment

* chore: remove comments

* chore: fix broken lock file

* feat: allow customization of hydrate / dehydrate options

and make sure we fall back to the defaultShouldDehydrate function, which only dehydrates successful queries

* release: v5.0.0-alpha.80

* docs: fix nextjs-streaming example

* fix(core) : sync Observer 'current' properties when optimistic reading occurs (#5611)

* fix-5538 : sync Observer 'current' properties when optimistic reading occurs

* Flip test on currentResult with placeholderData's order & add test

* Fix tests using the same queryKey

* remove options.placeHolderData from deciding whether to assign observer current properties, use equalitycheck on v5

* maybe fix for vue reactivity cbs

* test(vue-query): test persister with useQuery

* Force line terminator to \\n on codemods tests

* Revert " Force line terminator to \\n on codemods tests"

This reverts commit 6f0a469.

---------

Co-authored-by: Dominik Dorfmeister <[email protected]>
Co-authored-by: Damian Osipiuk <[email protected]>

* chore: Force line terminator to \\n on codemods tests (#5664)

Co-authored-by: Dominik Dorfmeister <[email protected]>

* chore: stabilize a flaky test

* release: v5.0.0-alpha.81

* docs: remove devtools from example

because they currently don't work

* fix(query-devtools): Force publish package (#5715)

* release: v5.0.0-alpha.82

* docs: re-enable devtools

* fix: Update dev dependencies (#5718)

* release: v5.0.0-alpha.83

* chore: Add vite to root package.json (#5722)

* refactor: Add new eslint sorting from main (#5723)

* release: v5.0.0-alpha.84

* chore: Update vite and vitest (#5724)

* chore: Remove eslint-plugin-compat (#5732)

* feat: include meta in query and mutation hydration (#5733)

* feat: include `meta` in query and mutation hydration

* test: tests for meta hydration

* chore: stabilize a flaky test

* chore: stabilize another flaky test

* release: v5.0.0-alpha.85

* fix(onlineManager): always initialize with `online: true` (#5714)

* fix(onlineManager): always initialize with `online: true`

instead of relying on navigator.onLine, because that indicator is broken AF in chrome

https://bugs.chromium.org/p/chromium/issues/list?q=navigator.online

* docs: document subscribe methods

* docs

* test: fix types in tests

setting to undefined is now illegal, so we have to reset to `true`, which is the default now

* fix(tests): switch from mocking navigator.onLine to mocking onlineManager.isOnline

* fix: offline toggle in devtools

it should now be enough to set online to true / false, without firing the event, because we always set & respect that value. we don't override the event handler, so real online / offline events might interfere here

* chore: fix tests

with the implementation of onlineManager, where we default to `true`, we need an explicit `'offline'` event to get it to false; otherwise, switching back to true doesn't change the state, so subscribers are not informed

* chore: prettier write

* chore: fix eslint

* chore: delete an old, flaky test that doesn't test much

* release: v5.0.0-alpha.86

* docs: use bundlejs for bundle-size

* docs: fix link

* feat: Replace rollup with tsup/esbuild (#5597)

Co-authored-by: Dominik Dorfmeister <[email protected]>
Co-authored-by: Aryan Deora <[email protected]>

* release: v5.0.0-alpha.87

* chore: Simplify tsconfig (#5745)

* fix: Simplify devDependencies (#5747)

* fix: Fix tsconfig "include" setting (#5750)

* release: v5.0.0-alpha.88

* docs: fix potential typo (#5748)

* fix potential typo

* Update docs/react/guides/queries.md

---------

Co-authored-by: Dominik Dorfmeister <[email protected]>

* fix: Add missing extensions to ESM imports (#5751)

* chore: Bundler integration tests (#5756)

* Add react-cra5 test

* Add react-cra4 test

* Add react-vite test

* Add svelte-vite test

* Add solid-vite test

* Run prettier

* Rename script to test:bundle

* Add vue-vite test

* Run prettier

* fix(query-devtools): Fix Devtools Build Issues (#5768)

* release: v5.0.0-alpha.89

* feat(codemod): add codemod that renames the `Hydrate` component usages to `HydrationBoundary` usages (#5761)

* feat(codemod): add codemod that renames the `cacheTime` and `useErrorBoundary` object properties and TypeScript property signatures (#5765)

* feat(react-query): useSuspenseQuery (#5739)

* feat: useSuspenseQuery

* feat: infiniteQueryOptions

* fix: add exports

* feat: useSuspenseInfiniteQuery

* feat: initialData overloads for useInfiniteQuery

* fix: types

* chore: stabilize test

we sometimes get failureCount: 2, but it doesn't matter here (timing issue)

* fix: types for useSuspenseQuery (#5755)

* docs: suspense

* docs: api reference

* docs: useSuspenseQuery in examples

* fix: types for useSuspenseInfiniteQuery (#5766)

---------

Co-authored-by: Jonghyeon Ko <[email protected]>

* release: v5.0.0-alpha.90

* chore: fix prettier

* chore: fix tests

* release: v5.0.0-alpha.91

---------

Signed-off-by: marbemac <[email protected]>
Signed-off-by: Eng Zer Jun <[email protected]>
Co-authored-by: Tanner Linsley <[email protected]>
Co-authored-by: Fredrik Höglund <[email protected]>
Co-authored-by: Gabriel Pichot <[email protected]>
Co-authored-by: Marc MacLeod <[email protected]>
Co-authored-by: Aryan Deora <[email protected]>
Co-authored-by: Eng Zer Jun <[email protected]>
Co-authored-by: Damian Osipiuk <[email protected]>
Co-authored-by: Arthur Denner <[email protected]>
Co-authored-by: Ilya <[email protected]>
Co-authored-by: Lachlan Collins <[email protected]>
Co-authored-by: OrJDev <[email protected]>
Co-authored-by: Enguerrand des Vaux <[email protected]>
Co-authored-by: Dennis kinuthia <[email protected]>
Co-authored-by: Yuji Sugiura <[email protected]>
Co-authored-by: Yaroslav Lapin <[email protected]>
Co-authored-by: Balázs Máté Petró <[email protected]>
Co-authored-by: Aleksandr Semenov <[email protected]>
Co-authored-by: Matthew Salsamendi <[email protected]>
Co-authored-by: Speros Kokenes <[email protected]>
Co-authored-by: EL AYADI Mohamed <[email protected]>
Co-authored-by: Dale Seo <[email protected]>
Co-authored-by: Jonghyeon Ko <[email protected]>
mvantellingen added a commit to labd/commercetools-node-mock that referenced this issue Jul 30, 2023
alecgibson added a commit to reedsy/mongodb-queue that referenced this issue May 7, 2024
Default exports have [bad interoperability][1] between Common JS and
ES Module imports, so the safest thing to do is just remove them.

This is a **BREAKING** change which removes our export default
statements, and adds a linter rule to prevent us from adding them.

[1]: evanw/esbuild#1719 (comment)
alecgibson added a commit to reedsy/mongodb-queue that referenced this issue May 7, 2024
Default exports have [bad interoperability][1] between Common JS and
ES Module imports, so the safest thing to do is just remove them.

This is a **BREAKING** change which removes our export default
statements, and adds a linter rule to prevent us from adding them.

[1]: evanw/esbuild#1719 (comment)
alecgibson added a commit to reedsy/mongodb-queue that referenced this issue May 7, 2024
Default exports have [bad interoperability][1] between Common JS and
ES Module imports, so the safest thing to do is just remove them.

This is a **BREAKING** change which removes our export default
statements, and adds a linter rule to prevent us from adding them.

[1]: evanw/esbuild#1719 (comment)
@JulianKingman
Copy link

Dear @evanw, you are a gentleman and a scholar. You have saved me this day, and enlightened me on the source of my sorrows. I don't know how you got such a deep understanding of ESM modules and the various build behaviors, but I'm sincerely grateful that you chose to share it in so much detail here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants