You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears the during SourceMap concat, we accidentally support absolute paths, but in Simple we do not. We should actually never support absolute paths, and that was merely a mistake.
People run into this, in ember via app.import(someAbsolutePath). And it leads to sadness and confusion, as often they run sourceMaps in dev, but not prod. Resulting in dev including the file and prod not. This sucks.
Two options:
a) We drop support for absolute paths and the rollout plan would be something like:
we warn when we see an absolute path today
we do a major version that changes this warn to an assert
profit
b) We add support uniformly for absolute paths.
The text was updated successfully, but these errors were encountered:
It appears the during SourceMap concat, we accidentally support absolute paths, but in Simple we do not. We should actually never support absolute paths, and that was merely a mistake.
People run into this, in ember via
app.import(someAbsolutePath)
. And it leads to sadness and confusion, as often they run sourceMaps in dev, but not prod. Resulting in dev including the file and prod not. This sucks.Two options:
a) We drop support for absolute paths and the rollout plan would be something like:
b) We add support uniformly for absolute paths.
The text was updated successfully, but these errors were encountered: