issues
search
Ravenstine
/
ember-custom-elements
The easiest way to render parts of your Ember app using custom elements.
MIT License
15
stars
4
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Fix ember router import
#21
arthurrsouza
closed
11 months ago
0
Could not find module `@ember/-internals/routing/lib/system/route` imported from `ember-custom-elements/route-connections`
#20
kevinkucharczyk
opened
1 year ago
0
Uncaught RangeError: Maximum call stack size exceeded - on specific app
#19
billyjov
opened
3 years ago
2
Muliples custom elements (full ember apps) have conflict inside host app
#18
billyjov
opened
3 years ago
2
[CHORE] Improve documentation structure
#17
Ravenstine
opened
3 years ago
0
docs: how to render an entire application as custom element in another apps
#16
billyjov
opened
3 years ago
12
Cacheing templates
#15
Ravenstine
opened
3 years ago
0
Support for native web components
#14
Ravenstine
opened
3 years ago
1
Broken with latest Ember release
#13
alexlafroscia
closed
3 years ago
4
Template-only components cause failure to boot application
#12
alexlafroscia
opened
4 years ago
4
fix: avoid relying on constructor name for `isGlimmerComponent` check
#11
alexlafroscia
closed
4 years ago
0
Implement support for use in add-ons
#10
Ravenstine
closed
4 years ago
0
Not compatible with production builds out-of-the-box
#9
alexlafroscia
closed
4 years ago
4
Compatibility with React components, Svelte, etc.
#8
Ravenstine
closed
3 years ago
1
fix: ensure `connectedCallback` runs after Ember initializer
#7
alexlafroscia
closed
4 years ago
3
Usage with Ember Addon Components
#6
alexlafroscia
closed
4 years ago
5
@__ARGS__?
#5
Ravenstine
opened
4 years ago
0
Shadow roots off by default?
#4
Ravenstine
closed
4 years ago
1
Needs a `getCustomElement` helper function
#3
Ravenstine
closed
4 years ago
1
Add global config
#2
Ravenstine
closed
4 years ago
0
Consider approach for named yields
#1
Ravenstine
opened
4 years ago
0