Asset was skipped or not found #6892
Comments
|
Can you provide a code sample that reproduces the issue? |
|
I got the same error. I think it occurred because of a conditional The workaround was to turn off scope hoisting. Also, would ne nice if this exception included the name of the asset: https://github.com/parcel-bundler/parcel/blob/v2/packages/packagers/js/src/ScopeHoistingPackager.js#L786 |
|
I just ran into this issue as well. I haven't dug into the issue, but I can confirm that add |
|
Experiencing the same issue. Weirdly adding |
|
I run into a same issue with Removing the line I tried to implement a simple reproducible repo but in a smaller code base it was still working without further issues. Someone has an idea how to find out more or what to look at? I unfortunately cannot share the original repository. |
|
This is very hard to reproduce because it depends on the order that dependencies are resolved in and generally on the shape of the asset graph. One helpful thing might be that this error and non-reproducible builds (where the bundle contents and therefore size/hash change between runs) usually have the same root cause (= the bug that's causing this). |
|
For me this happens with |
|
@mischnic I've reproduced this error: Parcel: "^2.0.1" Repo: https://github.com/TrackTak/parcel-watch-error How to reproduce:
output: |
mischnic
added
🐛 Bug
🕐 Waiting
✨ Parcel 2
🌳 Scope Hoisting
and removed
🕐 Waiting
labels
|
I'm running into the same error with Repo reproducing the error — https://github.com/flexdinesh/parcel-react-watch-error Node: v16.9.0 |
For library targets: - Skips applying refresh transforms in JSTransformer - Skips applying ReactRefreshRuntime - Skips applying transforms in ReactRefreshWrapTransformer - Adds test asserting that runtime and transforms are not applied Fixes #7359, #7496, #7652, #7900 See also: #6892 Co-authored-by: Niklas Mischkulnig <[email protected]>
|
#7914 will solve this for React library cases (/cc @MartinDawson @flexdinesh). There is still a more general problem that manifests as |
|
For me, this issue appears when I import |
|
We ran into this issue and it was caused by two re-exports of the same file. e.g. export * from './events';
import * as _Events from "./events";
export { _Events as Events };Removing one of the re-exports resolved the issue. |
|
Full reproduction for that (the error isn't thrown but the asset is still excluded incorrectly and the output JS is invalid) // index.js
import { c } from "./b.js";
console.log(c);
// b.js
export * from "./c.js";
import * as _a from "./c.js";
export { _a as c };
// c.js
export const a = 1;
export const b = 2;
// package.json
{
"sideEffects": ["index.js"]
}Output: (() => {
console.log((0, $c98c7015a51a9260$exports.c));
})();Somewhat related: #5255 One possible solution is modelling |
🐛 bug report
After upgraded to rc.0 and fixed bunch of errors and messages I see this message:
Asset was skipped or not found🎛 Configuration (.babelrc, package.json, cli command)
my .parcelrc
🤔 Expected Behavior
Building normally
😯 Current Behavior
🔦 Context
💻 Code Sample
🌍 Your Environment
I think it is not relevant to environment
The text was updated successfully, but these errors were encountered: