Official Semantic UI Integration for Ember

Semantic Org

Last update: Oct 1, 2022

Related tags

React Semantic-UI-Ember

Overview

Semantic-UI-Ember

This is the official Ember library for the Semantic-UI modules.

Support

The NodeJS and EmberJS versions respective tags are tested on. It might work with versions not listed as well

3.0

2.1

2.0

Installation

v3

Install this through Ember CLI. We support Ember 2.12 LTS through 3.x

ember install semantic-ui-ember

v2.1

Install this add-on through Ember CLI. We support Ember versions 2.x and above

NOTE: This is a bower-less install

ember install [email protected]

That's it.

v2.0 and below only

Install this add-on through Ember CLI. We support Ember versions 1.13 latest - 2.X.

NOTE: Ember 2.x only without fastboot is supported

ember install [email protected]

Run the library's blueprint to pull in its Bower dependencies. This only needs to be done once.

ember generate semantic-ui-ember

Documentation

Detailed documentation on using Semantic-UI-Ember.

Changelog

Comments

Allow custom semantic-ui builds

Adds two configuration options. One for the path to the dist folder of Semantic. The other option to specify the theme used for images and fonts.

Note that this does not add support for importing files outside of the build tree (e.g. bower_components). One can use bower link for local projects.

opened by khornberg 34
Changing the site theme not possible?

I have installed Semantic-UI-Ember into my ember-cli app and it looks like the default theme is working, however, I would like to change the default theme to one of the other prepackaged themes (like github).

It looks like your project is not using Gulp, which is what Semantic uses for its build, so I assume changing only the theme.config file will not work. In this case, why is it even necessary to include all the Semantic-UI project, rather than simply the default .css, .js and font files?

Is it intended that we can use the build tools in the semantic-ui directory ourselves?

Sorry if I am missing something obvious...new to this system. ;^)

opened by Panoplos 23
Two outdated dependensies
See: https://david-dm.org/Semantic-Org/Semantic-UI-Ember

^5.1.7 6.4.1 7.0.0-alpha.2``` ```ember-runtime-enumerable-includes-polyfill ^1.0.1 2.0.0 2.0.0
opened by w96k 17

Asset path for themes with less

How to properly resolve theme assets using ember-cli-less?

Build file specifies: fonts: 'assets/themes/default/assets/fonts' and writes them there accordingly.

However, Semantic is looking the the wrong path, outside of assets folder, and 404s for fonts, et.c /themes/default/assets/fonts/icons.ttf

SemanticUI: {
  // These flags allow you do turn on or off auto imports for Semantic UI
  import: {
        css: false,
        javascript: true,
        image: true,
        fonts: true
  },
  // These settings allow you to specify the source of the Semantic files
  source: {
    css: 'bower_components/semantic-ui/dist',
    javascript: 'bower_components/semantic-ui/dist',
    images: 'bower_components/semantic-ui/dist/themes/default/assets/images',
    fonts: 'bower_components/semantic-ui/dist/themes/default/assets/fonts'
  },
  // These settings allow you to specify the destination of the Semantic files
  // This only applies to images and fonts, since those are assets
  destination: {
    images: 'assets/themes/default/assets/images',
    fonts: 'assets/themes/default/assets/fonts'
  }
}

If I change theme.config to use material theme for everything:

Semantic is looking not only outside of assets, but also for the material subfolder: /themes/material/assets/fonts/icons.woff

and fonts are written into default theme instead of material folder: assets/themes/default/assets/fonts

WORK AROUND: for default theme: (build file)

      destination: {
        images: 'themes/default/assets/images', 
        fonts: 'themes/default/assets/fonts'
      }

However, same work around doesn't work if using material theme for all settings in themes.config. eg.

      destination: {
        images: 'themes/material/assets/images', //defaults to: 'assets/themes/default/assets/images', but semantic isn't looking there.
        fonts: 'themes/material/assets/fonts'
      }

The font files are loaded, eg. /themes/material/assets/fonts/icons.woff2, however they aren't display, just a square icon shows up instead.

The CSS compiled seems to match however.

@font-face {
  font-family: 'Icons';
  src: url("../../themes/material/assets/fonts/icons.eot");
  src: url("../../themes/material/assets/fonts/icons.eot?#iefix") format('embedded-opentype'), url("../../themes/material/assets/fonts/icons.woff2") format('woff2'), url("../../themes/material/assets/fonts/icons.woff") format('woff'), url("../../themes/material/assets/fonts/icons.ttf") format('truetype'), url("../../themes/material/assets/fonts/icons.svg#icons") format('svg');
  font-style: normal;
  font-weight: normal;
  font-variant: normal;
  text-decoration: inherit;
  text-transform: none;
}

IDEALLY, shouldn't the CSS always get compiled to match the :destination: in the build-config, or perhaps have the :destination: generated based on the current theme?

Setup references: https://github.com/nathanpalmer/example-semantic-ui-ember-cli http://semantic-org.github.io/Semantic-UI-Ember/#/modules/usage

opened by danDanV1 15

Checkbox's 'checked' no longer mutable?
After upgrading to the recent beta, the checkbox no longer seems to activate its checked variable properly. The variable assigned to 'checked' seems somehow no longer mutable.

{{ui-checkbox checked=checkTest label="test" onChange=(action 'toggleCheck')}} {{checkTest}} <---- always a static value, even when the checkbox is triggered (and is visually toggled from true/false).

If: export default Ember.Controller.extend({checkTest: true} Then the checkbox will be rendered properly, as true, but will still not update when a user checks the checkbox.
opened by jfarlow 15
How to use Sidebar with Ember 2 components
Hi,

Your Sidebar documentation instructs to create an application component/view. However, I am unaware of how to create an application component (if that's possible in Ember 2) and views are deprecated.

By following the rest of the instructions, the sidebar now works. However, the these errors come up in the console:

Sidebar: Had to add pusher element. For optimal performance make sure body content is inside a pusher element

Sidebar: Had to move sidebar. For optimal performance make sure sidebar and pusher are direct children of your body tag

I have a pusher element, but I don't know how I can create an application view/component in Ember 2, so what's the supported way to get this to work?

Thanks so much,

Justin
opened by xtagon 15
Ember and Semantic Upgrades
Everything on this list is complete. I'll just want to run through some additional tests before we merge it in. This does include several breaking changes though so any feedback is helpful.

Ember Upgrade

The latest version of Ember brings deprecations and incompatibilities with this library. It's mostly because we were piggy-backing on their internal helpers.

[x] Upgrade to Ember 1.13

[x] Verify it works with Ember 2.0

[x] Make sure we're DDAU (Data Down Action Up)

[x] Update Dropdown to be compatible without Ember.Select

[x] Update Modal to remove usage of Ember.View

Semantic Upgrade

We need to ensure that this is compatible with Semantic 2.0

[x] Upgrade to Semantic 2.0

[x] Optional css/js/font includes

[x] Semantic Theme Support

Components

Here to finish out support for any components we're missing. Most are marked with a question-mark so we can decide whether it adds value to implement.

[x] Accordion

[x] Checkbox

[x] Dimmer (no component, can be called directly)

[x] Dropdown

[x] Embed

[x] Modal

[x] Nag

[x] Popup

[x] Progress

[x] Radio

[x] Rating

[x] Search

[x] Shape

[x] Sidebar

[x] Sticky

[x] Tab (no component, use ember routes instead)

[x] Transition (no component, can be called directly)

Tests

When this was first released it was used in 2+ production apps so we knew everything was working as expected. Now we need to add tests to ensure we aren't introducing regressions.

[x] Add Tests for Accordion

[x] Add Tests for Checkbox

[x] Add Tests for Dropdown

[x] Add Tests for Embed

[x] Add Tests for Modal

[x] Add Tests for Nag

[x] Add Tests for Popup

[x] Add Tests for Progress

[x] Add Tests for Radio

[x] Add Tests for Rating

[x] Add Tests for Search

[x] Add Tests for Shape

[x] Add Tests for Sidebar

[x] Add Tests for Sticky

Breaking Changes

Dropdown

The dropdown has probably the most significant changes to it since it was previously using the Ember.Select view that doesn't exist today. Instead we've gone light-weight and out of the way. What the means is the ui-dropdown must specify the content which gives you the greatest flexibility and allows you to follow semantic-ui docs.

{{#ui-dropdown class="selection" value=gender}} <div class="default text">Gender</div> <i class="dropdown icon"></i> <div class="menu"> {{#each genders as |gender|}} <div class="item" data-value={{gender.id}}> {{gender.text}} </div> {{/each}} </div> {{/ui-dropdown}}

Binding value to gender ensures that whatever semantic is spitting out for values (based on the data-value binding above) is what gets set.

You can also follow DDAU (Data Down Action Up) by specifying an action here instead.

{{#ui-dropdown class="selection" onChange=(action 'update_gender')}}

If you want to bind to an object instead of a value you'll need to use the ``{{ui-dropdown-item}}` component like this.

{{#ui-dropdown class="selection" value=gender2}} <div class="default text">Gender</div> <i class="dropdown icon"></i> <div class="menu"> {{#each genders as |gender|}} {{#ui-dropdown-item content=gender}} {{gender.text}} {{/ui-dropdown-item}} {{/each}} </div> {{/ui-dropdown}}

Modal

Modals are now components and much like semantic-ui's master documentation they need to be placed on the page they will be invoked on.

{{#ui-modal name="profile" class="profile" approve=(action 'approveModal') deny=(action 'denyModal')}} <i class="close icon"></i> <div class="header"> Profile Picture </div> <div class="image content"> <div class="ui medium image"> <img src="http://semantic-ui.com/images/avatar/large/chris.jpg"> </div> <div class="description"> <div class="ui header">We've auto-chosen a profile image for you.</div> <p>We've grabbed the following image from the <a href="https://www.gravatar.com" target="_blank">gravatar</a> image associated with your registered e-mail address.</p> <p>Is it okay to use this photo?</p> </div> </div> <div class="actions"> <div class="ui black deny button"> Nope </div> <div class="ui positive right labeled icon button"> Yep, that's me <i class="checkmark icon"></i> </div> </div> {{/ui-modal}}

You can invoke this using the standard $('.ui.modal').modal('show')
opened by nathanpalmer 14

Unknown feature "default-async-observers" found in config/optional-features.json

Unknown feature "default-async-observers" found in config/optional-features.json

An error occurred in the constructor for @ember/optional-features at /Users/<username>/projects/<project_name>/node_modules/semantic-ui-ember/node_modules/@ember/optional-features

An error occurred in the constructor for semantic-ui-ember at /Users/<username>/projects/<project_name>/node_modules/semantic-ui-ember

Seeing this error on a fresh install of [email protected]. Any ideas why?

opened by ozywuli 13

Generate custom ui theme blueprint crashes

When running ember generate semantic-ui-custom, it crashes with the following error message. I'm on ember 3.0 and semantic-ui-ember 3.0.

ERROR Summary:

  - broccoliBuilderErrorStack: [undefined]
  - codeFrame: [undefined]
  - errorMessage: Cannot read property 'then' of undefined
  - errorType: [undefined]
  - location:
    - column: [undefined]
    - file: [undefined]
    - line: [undefined]
  - message: Cannot read property 'then' of undefined
  - name: TypeError
  - nodeAnnotation: [undefined]
  - nodeName: [undefined]
  - originalErrorMessage: [undefined]
  - stack: TypeError: Cannot read property 'then' of undefined
    at Class.afterInstall (C:\Users\Bouke\Developer\yarn-test\node_modules\semantic-ui-ember\blueprints\semantic-ui-custom\index.js:11:53)
    at tryCatcher (C:\Users\Bouke\Developer\yarn-test\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:323:19)
    at invokeCallback (C:\Users\Bouke\Developer\yarn-test\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:495:31)
    at publish (C:\Users\Bouke\Developer\yarn-test\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:481:7)
    at flush (C:\Users\Bouke\Developer\yarn-test\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:2402:5)
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)

bug

opened by Bouke 13

Icon files have the wrong path and are not found (404)

Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:4200/themes/default/assets/fonts/icons.woff Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:4200/themes/default/assets/fonts/icons.ttf Failed to load resource: the server responded with a status of 404 (Not Found)

Icons are not showing. I have my set up with LESS support, an app.less and theme.less file, and a theme.config file.

opened by charlwillia6 13
Skip `getSemanticModule` in fastboot mode

In fastboot mode, Accessingthis.elementis not allowed in non-interactive environments (such as FastBoot). error is thrown due to the calling of getSemanticScope (since it tries to access the jQuery element) via the getSemanticModule call present in the execute method.

Follow up to #204 Resolves #100

opened by niranjan94 12
Bump express from 4.16.2 to 4.18.2
Bumps express from 4.16.2 to 4.18.2.

Release notes

Sourced from express's releases.

4.18.2

Fix regression routing a large stack in a single route

deps: [email protected]

deps: [email protected]

perf: remove unnecessary object clone

deps: [email protected]

4.18.1

Fix hanging on large stack of sync routes

4.18.0

Add "root" option to res.download

Allow options without filename in res.download

Deprecate string and non-integer arguments to res.status

Fix behavior of null/undefined as maxAge in res.cookie

Fix handling very large stacks of sync middleware

Ignore Object.prototype values in settings through app.set/app.get

Invoke default with same arguments as types in res.format

Support proper 205 responses using res.send

Use http-errors for res.format error

deps: [email protected]

Fix error message for json parse whitespace in strict

Fix internal error when inflated body exceeds limit

Prevent loss of async hooks context

Prevent hanging when request already read

deps: [email protected]

deps: [email protected]

deps: [email protected]

deps: [email protected]

deps: [email protected]

deps: [email protected]

Add priority option

Fix expires option to reject invalid dates

deps: [email protected]

Replace internal eval usage with Function constructor

Use instance methods on process to check for listeners

deps: [email protected]

Remove set content headers that break response

deps: [email protected]

deps: [email protected]

deps: [email protected]

Prevent loss of async hooks context

deps: [email protected]

deps: [email protected]

Fix emitted 416 error missing headers property

Limit the headers removed for 304 response

deps: [email protected]

deps: [email protected]

deps: [email protected]

deps: [email protected]

... (truncated)

Changelog

Sourced from express's changelog.

4.18.2 / 2022-10-08

Fix regression routing a large stack in a single route

deps: [email protected]

deps: [email protected]

perf: remove unnecessary object clone

deps: [email protected]

4.18.1 / 2022-04-29

Fix hanging on large stack of sync routes

4.18.0 / 2022-04-25

Add "root" option to res.download

Allow options without filename in res.download

Deprecate string and non-integer arguments to res.status

Fix behavior of null/undefined as maxAge in res.cookie

Fix handling very large stacks of sync middleware

Ignore Object.prototype values in settings through app.set/app.get

Invoke default with same arguments as types in res.format

Support proper 205 responses using res.send

Use http-errors for res.format error

deps: [email protected]

Fix error message for json parse whitespace in strict

Fix internal error when inflated body exceeds limit

Prevent loss of async hooks context

Prevent hanging when request already read

deps: [email protected]

deps: [email protected]

deps: [email protected]

deps: [email protected]

deps: [email protected]

deps: [email protected]

Add priority option

Fix expires option to reject invalid dates

deps: [email protected]

Replace internal eval usage with Function constructor

Use instance methods on process to check for listeners

deps: [email protected]

Remove set content headers that break response

deps: [email protected]

deps: [email protected]

deps: [email protected]

Prevent loss of async hooks context

deps: [email protected]

deps: [email protected]

... (truncated)

Commits

8368dc1 4.18.2

61f4049 docs: replace Freenode with Libera Chat

bb7907b build: [email protected]

f56ce73 build: [email protected]

24b3dc5 deps: [email protected]

689d175 deps: [email protected]

340be0f build: [email protected]

33e8dc3 docs: use Node.js name style

644f646 build: [email protected]

ecd7572 build: [email protected]

Additional commits viewable in compare view

Dependabot 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)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump qs from 6.4.0 to 6.4.1
Bumps qs from 6.4.0 to 6.4.1.

Changelog

Sourced from qs's changelog.

6.4.1

[Fix] parse: ignore __proto__ keys (#428)

[Fix] fix for an impossible situation: when the formatter is called with a non-string value

[Fix] use safer-buffer instead of Buffer constructor

[Fix] utils.merge: avoid a crash with a null target and an array source

[Fix] utils.merge`: avoid a crash with a null target and a truthy non-array source

[Fix] stringify: fix a crash with strictNullHandling and a custom filter/serializeDate (#279)

[Fix] utils: merge: fix crash when source is a truthy primitive & no options are provided

[Fix] when parseArrays is false, properly handle keys ending in []

[Robustness] stringify: avoid relying on a global undefined (#427)

[Refactor] use cached Array.isArray

[Refactor] stringify: Avoid arr = arr.concat(...), push to the existing instance (#269)

[readme] remove travis badge; add github actions/codecov badges; update URLs

[Docs] Clarify the need for "arrayLimit" option

[meta] fix README.md (#399)

[meta] Clean up license text so it’s properly detected as BSD-3-Clause

[meta] add FUNDING.yml

[actions] backport actions from main

[Tests] remove nonexistent tape option

[Dev Deps] backport from main

Commits

486aa46 v6.4.1

727ef5d [Fix] parse: ignore __proto__ keys (#428)

cd1874e [Robustness] stringify: avoid relying on a global undefined (#427)

45e987c [readme] remove travis badge; add github actions/codecov badges; update URLs

90a3bce [meta] fix README.md (#399)

9566d25 [Fix] fix for an impossible situation: when the formatter is called with a no...

74227ef Clean up license text so it’s properly detected as BSD-3-Clause

35dfb22 [actions] backport actions from main

7d4670f [Dev Deps] backport from main

0485440 [Fix] use safer-buffer instead of Buffer constructor

Additional commits viewable in compare view

Dependabot 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)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump decode-uri-component from 0.2.0 to 0.2.2
Bumps decode-uri-component from 0.2.0 to 0.2.2.

Release notes

Sourced from decode-uri-component's releases.

v0.2.2

Prevent overwriting previously decoded tokens 980e0bf

https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2

v0.2.1

Switch to GitHub workflows 76abc93

Fix issue where decode throws - fixes #6 746ca5d

Update license (#1) 486d7e2

Tidelift tasks a650457

Meta tweaks 66e1c28

https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1

Commits

a0eea46 0.2.2

980e0bf Prevent overwriting previously decoded tokens

3c8a373 0.2.1

76abc93 Switch to GitHub workflows

746ca5d Fix issue where decode throws - fixes #6

486d7e2 Update license (#1)

a650457 Tidelift tasks

66e1c28 Meta tweaks

See full diff in compare view

Dependabot 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)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump engine.io and testem
Bumps engine.io and testem. These dependencies needed to be updated together. Updates engine.io from 1.8.0 to 3.6.1

Release notes

Sourced from engine.io's releases.

3.6.1

:warning: This release contains an important security fix :warning:

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

Error: read ECONNRESET at TCP.onStreamRead (internal/stream_base_commons.js:209:20) Emitted 'error' event on Socket instance at: at emitErrorNT (internal/streams/destroy.js:106:8) at emitErrorCloseNT (internal/streams/destroy.js:74:3) at processTicksAndRejections (internal/process/task_queues.js:80:21) { errno: -104, code: 'ECONNRESET', syscall: 'read' }

Please upgrade as soon as possible.

Bug Fixes

catch errors when destroying invalid upgrades (83c4071)

3.6.0

Bug Fixes

add extension in the package.json main entry (#608) (3ad0567)

do not reset the ping timer after upgrade (1f5d469)

Features

decrease the default value of maxHttpBufferSize (58e274c)

This change reduces the default value from 100 mb to a more sane 1 mb.

This helps protect the server against denial of service attacks by malicious clients sending huge amounts of data.

See also: https://github.com/advisories/GHSA-j4f2-536g-r55m

increase the default value of pingTimeout (f55a79a)

Links

Diff: https://github.com/socketio/engine.io/compare/3.5.0...3.6.0

Client release: -

... (truncated)

Changelog

Sourced from engine.io's changelog.

3.6.1 (2022-11-20)

:warning: This release contains an important security fix :warning:

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

Error: read ECONNRESET at TCP.onStreamRead (internal/stream_base_commons.js:209:20) Emitted 'error' event on Socket instance at: at emitErrorNT (internal/streams/destroy.js:106:8) at emitErrorCloseNT (internal/streams/destroy.js:74:3) at processTicksAndRejections (internal/process/task_queues.js:80:21) { errno: -104, code: 'ECONNRESET', syscall: 'read' }

Please upgrade as soon as possible.

Bug Fixes

catch errors when destroying invalid upgrades (83c4071)

6.2.1 (2022-11-20)

:warning: This release contains an important security fix :warning:

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

Error: read ECONNRESET at TCP.onStreamRead (internal/stream_base_commons.js:209:20) Emitted 'error' event on Socket instance at: at emitErrorNT (internal/streams/destroy.js:106:8) at emitErrorCloseNT (internal/streams/destroy.js:74:3) at processTicksAndRejections (internal/process/task_queues.js:80:21) { errno: -104, code: 'ECONNRESET', syscall: 'read' }

Please upgrade as soon as possible.

Bug Fixes

... (truncated)

Commits

67a3a87 chore(release): 3.6.1

83c4071 fix: catch errors when destroying invalid upgrades

f62f265 chore(release): 3.6.0

f55a79a feat: increase the default value of pingTimeout

1f5d469 fix: do not reset the ping timer after upgrade

3ad0567 fix: add extension in the package.json main entry (#608)

58e274c feat: decrease the default value of maxHttpBufferSize

b9dee7b chore(release): 3.5.0

19cc582 feat: add support for all cookie options

5ad2736 feat: disable perMessageDeflate by default

Additional commits viewable in compare view

Updates testem from 2.0.0 to 2.17.0

Release notes

Sourced from testem's releases.

Compression!

[FEATURE] ensure the express server gzip's assets it serves (For large applications, this has seen to reduce assets loaded during tests by up to 84%)

[Enhancement] improve custom reporter code snippets

[Internal] Fix electron tests on travis

[Internal] add phantomjs as a devDependency so tests pass without phantom being ambiently installed.

v2.16.0

Fix: if the socket disconnects, reconnect with browser-login event with the new socket

Cleanup: Moving util files into /util

v2.15.1

BUGFIX: Issue 1336 - non string expected cause failure in xunit reporter

v2.15.0

Improve browser console log & add console.group as additional method to interrupt

[XUnit] Show info about failed assertion

Commits

03d20d1 release v2.17.0 🎉

dd5e654 Merge pull request #1351 from astronomersiva/master

c7ecc85 Add libgconf-2-4 to Travis to get Electron running in tests

fa311a6 Merge pull request #1349 from davecombs/master

e2a276e updated to make phantomjs a devDependency, now bin/run-tests.js passes locally

b305c8f added compression() to testem express server

176bf5b Merge pull request #1345 from Turbo87/patch-1

3d208f8 docs/custom_reporters: Improve code snippets

80936fd release v2.16.0 🎉

5e24ebe Merge pull request #1340 from step2yeung/recon

Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by stefanpenner, a new releaser for testem since your current version.

Dependabot 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)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump socket.io-parser and testem
Bumps socket.io-parser and testem. These dependencies needed to be updated together. Updates socket.io-parser from 2.3.1 to 3.4.2

Release notes

Sourced from socket.io-parser's releases.

3.4.1

Bug Fixes

prevent DoS (OOM) via massive packets (#95) (dcb942d)

Links

Milestone: -

Diff: 3.4.0...3.4.1

3.4.0

This release mostly contains a bump of the debug package.

Links

Milestone: -

Diff: 3.3.0...3.4.0

3.3.2

Bug Fixes

prevent DoS (OOM) via massive packets (#95) (89197a0)

Links

Diff: https://github.com/Automattic/socket.io-parser/compare/3.3.1...3.3.2

3.3.1

Links

Diff: https://github.com/socketio/socket.io-parser/compare/3.3.0...3.3.1

3.3.0

Bug Fixes

remove any reference to the global variable (b47efb2)

Links

Milestone: -

Diff: 3.2.0...3.3.0

3.2.0

Bug fixes

properly detect typed arrays (#85)

properly handle JSON.stringify errors (#84)

Note

... (truncated)

Changelog

Sourced from socket.io-parser's changelog.

3.4.2 (2022-11-09)

Bug Fixes

check the format of the index of each attachment (04d23ce)

4.2.1 (2022-06-27)

Bug Fixes

check the format of the index of each attachment (b5d0cb7)

4.0.5 (2022-06-27)

Bug Fixes

check the format of the index of each attachment (b559f05)

4.2.0 (2022-04-17)

Features

allow the usage of custom replacer and reviver (#112) (b08bc1a)

4.1.2 (2022-02-17)

Bug Fixes

allow objects with a null prototype in binary packets (#114) (7f6b262)

4.1.1 (2021-10-14)

4.1.0 (2021-10-11)

... (truncated)

Commits

4b3c191 chore(release): 3.4.2

04d23ce fix: check the format of the index of each attachment

6a59237 test: add Node.js 12 and 14 in the build matrix

a8130ce chore: release 3.4.1

dcb942d fix: prevent DoS (OOM) via massive packets (#95)

a5d0435 test: transpile to es5 with babelify

652402a [chore] Release 3.4.0

9b3572e [chore] Bump debug to version 4.1.0 (#92)

de1fd36 [docs] Fix incorrect socket.io-protocol version in Readme (#89)

0de72b9 [chore] Release 3.3.0

Additional commits viewable in compare view

Updates testem from 2.0.0 to 2.17.0

Release notes

Sourced from testem's releases.

Compression!

[FEATURE] ensure the express server gzip's assets it serves (For large applications, this has seen to reduce assets loaded during tests by up to 84%)

[Enhancement] improve custom reporter code snippets

[Internal] Fix electron tests on travis

[Internal] add phantomjs as a devDependency so tests pass without phantom being ambiently installed.

v2.16.0

Fix: if the socket disconnects, reconnect with browser-login event with the new socket

Cleanup: Moving util files into /util

v2.15.1

BUGFIX: Issue 1336 - non string expected cause failure in xunit reporter

v2.15.0

Improve browser console log & add console.group as additional method to interrupt

[XUnit] Show info about failed assertion

Commits

03d20d1 release v2.17.0 🎉

dd5e654 Merge pull request #1351 from astronomersiva/master

c7ecc85 Add libgconf-2-4 to Travis to get Electron running in tests

fa311a6 Merge pull request #1349 from davecombs/master

e2a276e updated to make phantomjs a devDependency, now bin/run-tests.js passes locally

b305c8f added compression() to testem express server

176bf5b Merge pull request #1345 from Turbo87/patch-1

3d208f8 docs/custom_reporters: Improve code snippets

80936fd release v2.16.0 🎉

5e24ebe Merge pull request #1340 from step2yeung/recon

Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by stefanpenner, a new releaser for testem since your current version.

Dependabot 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)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0

Releases(v3.0.4)

v3.0.4(Dec 18, 2020)
Bump @ember/optional-features dependency.

Source code(tar.gz)
Source code(zip)
2.0.1(Jan 7, 2017)

Source code(tar.gz)
Source code(zip)
2.0.0(Oct 19, 2016)

Thank you for all the feedback and testing.
Source code(tar.gz)
Source code(zip)
2.0.0-beta.3(Oct 13, 2016)
Fixed

hasOwnProperty now properly works for objects without prototype

Updating tests for Glimmer 2

Source code(tar.gz)
Source code(zip)
2.0.0-beta.2(Oct 3, 2016)

Changes isHTMLSafe to a package dependency
Source code(tar.gz)
Source code(zip)
2.0.0-beta.1(Oct 1, 2016)
If there are no other reported issues in the next week, we'll release the 2.0.0 official release.

[2.0.0-beta.1]

Added

Allowing better configuration for customization https://github.com/Semantic-Org/Semantic-UI-Ember/pull/141

Fixed

Popup: only update attributes passed in

Popup: unwrap html safe values

Popup: don't update position

Base Mixin: added attribute bindings for autofocus, tabindex, title

Base Mixin: upwrap html safe values

Base Mixin: fix contains deprecation https://github.com/Semantic-Org/Semantic-UI-Ember/pull/143

Internal Changes

Updating Ember, Ember Data, and Ember CLI to 2.8

Updating multiple dependencies to latest version

Adding additional ember try versions

Moved promise tools to external addon

Fixed build https://github.com/Semantic-Org/Semantic-UI-Ember/pull/151

Source code(tar.gz)
Source code(zip)
2.0.0-beta.0(Jul 26, 2016)

After a few months of development and testing, we have released 2.0 beta.

While most of the changes are compatible with the 1.0 branch, there are some specific changes that you need to be aware of when upgrading. Please review the upgrade section.

Overall this is a big step forward for Semantic-UI-Ember. It is optimized to update properties directly on Semantic modules, avoid re-render issues, and improve performance. In addition, we were able to remove a lot of the work arounds in 1.0 like prefixing some names with ui_.

The biggest change is as the release name states, everything is now Data Down Actions Up. Properties are no longer mutated directly, but instead must be updated from the change events. This offers more control and flexibility in deciding what actions you want to take in response to events.

The last big change was in the documentation. We have moved all the documentation out of the readme into a stand alone site. We matched the look and feel of the existing Semantic-UI documentation. This should provide better documentation and easier navigation. Enjoy
Source code(tar.gz)
Source code(zip)
1.0(May 5, 2016)

We heard Data Down Actions Up was the next big thing, and so we've decided to hop on the bandwagon.

In all seriousness, we wanted to finalize the code as it stood today for the 1.0 releases, so that we could make the needed changes to move to a DDAU architecture for the 2.0 release.

We will continue to support 1.0 with bug fixes for the next six months, but any new or remaining features will be implemented on the 2.0 branch.
Source code(tar.gz)
Source code(zip)
v0.9.3(Jan 22, 2016)
#78: Fixed how we're building our constants so it's more compatible with Ember 2.3

Source code(tar.gz)
Source code(zip)
v0.9.2(Dec 15, 2015)
#75: Fixed a regression when value is used for binding to dropdowns @nathanpalmer

Source code(tar.gz)
Source code(zip)
v0.9.1(Dec 13, 2015)
This release brings a few fixes around dropdowns. The biggest is the deprecation of binding to value on ui-dropdown. This is because of how semantic treats setting the value on a dropdown. Refer to their documentation for additional information but in short setting a value on a dropdown does not update the interface.

Small fix to onChange action syntax for ui-dropdown

Fixing dropdown when there isn't an element

Don't get set properties on modules that don't have them

Deprecating binding to value on ui-dropdowns

Source code(tar.gz)
Source code(zip)
0.9.0(Dec 13, 2015)

You can find more information on the pull request.

This release bring compatibility with the latest version of Ember along with Semantic UI. In addition adds support to the rest of the components and brings a suite of tests as well!
Source code(tar.gz)
Source code(zip)