[addon-dev] Allow TS files in publicEntrypoints / appReexports
See original GitHub issueFor addons authoring their code in TS (or soon gjs/gts), currently is not possible to use @embroider/addon-dev
’s publicEntrypoints
or appReexports
methods.
We cannot use them because the dist files will end up with the same extension as the input.
In glimmer-apollo, I ended up doing a simple replace of .ts
with .js
.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
What is the resolution for these types of errors: <addon ...
My package's files / entrypoints are only an index.ts and registration.ts -- the index.ts doesn't do anything with xstate, it's only a single...
Read more >Module parse failed: Unexpected token Emberjs
It's a component addon with the co-location layout and typescript in ... is when I disable the declaration of ts files in the...
Read more >Migrating an Ember addon to the next-gen v2 format
This blog post walks you through the migration of an existing addon to Embroider's new v2 format.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think the solution in #1099 is solid~ish, but I need to figure out a peerDep issue – https://github.com/embroider-build/embroider/issues/1062 I think I’m getting two copies of
xstate
in the consuming app, and it’s only revealing itself because of component-manager’s reliance on object identity. 🤔@rwjblue PR here: https://github.com/embroider-build/embroider/pull/1106