`@` import paths require upstream dependencies
See original GitHub issuethe new import paths in #315 are incompatible with upstream addons if they don’t haven’t updated both ember-cli-babel
and ember-cli-htmlbars-inline-precompile
. might want to make a note of that.
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
How do I reference a dependency from an upstream package?
Imagine I have a package called commonPackage: import PackageDescription let package = Package( name: "commonPackage", dependencies: ...
Read more >proposal: Go 2: cmd/go: allow relative imports #20883 - GitHub
I have to change all the import paths of these dependencies if they use the import path like the above case. 20
Read more >Managing Dependencies, Forks, and Code Patches with Dep
With dep, we can address the first scenario with a single line. In our Gopkg.toml, we can use a source entry to specify...
Read more >Using forked package import in Go - Stack Overflow
The answer to this is that if you fork a repo with multiple packages you will need to rename all the relevant import...
Read more >Dependencies UI: View an entity's upstream and downstream ...
It shows upstream and downstream dependencies, and provides paths to explore them. While service maps displays an entity-scoped map of an entity's relationships ......
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 Free
Top 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
This has been fixed in #328
yeah I’m using beta.1, but even in a new ember project, I’m not seeing the
addon-test-support/helpers.js
file