insidewhy/queueing-subject

an rxjs subject that queues data when it has no observers

queueing-subject

The QueueingSubject is very similar to the ReplaySubject but it only queues values when it has no observers. The queued values are delivered to the first observer that subscribes at which point the queue is reset.

Changelog

Changelog here

queueing-subject's Issues

TypeError in constructor of QueueingSubject

When choosing es2015 as target language in our Angular 8 Typescript project we get the following runtime error with version 0.3.0:

ERROR Error: Uncaught (in promise): TypeError: Class constructor Subject cannot be invoked without 'new'
TypeError: Class constructor Subject cannot be invoked without 'new'
    at new QueueingSubject (index.js:17)

Inlining the code of the class QueueingSubject seems to be working, but using the npm package does not.

ES5 browsers not supported by queueing-subject by angular 8's legacy build

After upgrading to angular8 we were forcing the same problems as in #19. After the fix, tests show that it's not working in internet explorer 11.

minimal reproduction: https://github.com/dklmuc/queueing-subject-angular8

IE11 shows error in main-es5 bundle because of non ES5 compatible code:
Ja=function(){return function(){}}();class $a extends M{constructor(){super(...arguments),this.queuedValues=[]}next(t){this.closed||this.observers.length?super.next(t):this.queuedValues.push(t)}_subscribe(t){const

The same also when completly disable differential loading (changing target to es5 and remove browserlist file).

Release with rxjs6

Hi, I see you updated rxjs6 and typescript in the project, maybe you need to create fresh release with this changes.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update Node.js to v17
• Update dependency eslint-config-prettier to v9
• Update dependency husky to v9
• Update dependency prettier to v3
• Update dependency pretty-quick to v4
• Update dependency typescript to v5
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• Update dependency husky to v7.0.4
• Update dependency eslint to v7.32.0
• Update dependency pretty-quick to v3.3.1
• Update typescript-eslint monorepo to v4.33.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency eslint-config-prettier to v8.10.0
• Update dependency prettier to v2.8.8
• Update dependency rxjs to v7.8.1
• Update dependency typescript to v4.9.5
• Update dependency eslint to v8
• Update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

circleci

.circleci/config.yml

• circleci/node 10

npm

package.json

• @typescript-eslint/eslint-plugin 4.28.4
• @typescript-eslint/parser 4.28.4
• eslint 7.31.0
• eslint-config-prettier 8.3.0
• husky 7.0.1
• prettier 2.3.2
• pretty-quick 3.1.1
• rxjs 7.2.0
• typescript 4.3.5
• rxjs ^7

---

• Check this box to trigger a request for Renovate to run again on this repository

Target ES5 not working with angular8

Reopen of #22

When simply targeting ES5 in tsconfig, the builded bundle is not ES5-compatible. You see stuff like extends or spread operator in it.

see branch es5 in minimal reproduction: https://github.com/dklmuc/queueing-subject-angular8/tree/es5

RxJS 7+

Same thing for insidewhy/rxjs-websockets#188 as its used in the example. Its not a deal breaker, so if you can find the time 😄

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.