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
When writing out a metadata file, the imports -> path fields are wrong and appear to have doubled the --public-path value. Seems like this may be related to #524, but either way I've put together a reproduction repository. Pull that down, run npm install and then this command (it's also in the repro repo):
And take a look at the metafile's contents. You'll see that each outputs entry's imports path look like assets/assets/chunk* where it should only include assets once.
When writing out a metadata file, the
imports -> path
fields are wrong and appear to have doubled the--public-path
value. Seems like this may be related to #524, but either way I've put together a reproduction repository. Pull that down, runnpm install
and then this command (it's also in the repro repo):And take a look at the metafile's contents. You'll see that each
outputs
entry'simports
path look likeassets/assets/chunk*
where it should only includeassets
once.The text was updated successfully, but these errors were encountered: