Bump tar from 6.1.13 to removed in /browser_library_test in the npm_and_yarn group across 1 directory#193
Conversation
dependabot
bot
added
dependencies
|
@dependabot recreate |
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/browser_library_test/npm_and_yarn-eff1590ef8
branch
from
b24c7df to
f258698
Compare
|
@dependabot recreate |
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/browser_library_test/npm_and_yarn-eff1590ef8
branch
from
f258698 to
10f3276
Compare
|
I was so confused why this was causing an error. It turns out that the repo is already failing at HEAD ! |
|
@dependabot recreate the underlying bug has been fixed on main, so this should now pass.. or at the very least fail in a more obvious way |
Bumps the npm_and_yarn group with 1 update in the /browser_library_test directory: [tar](https://github.com/isaacs/node-tar). Removes `tar` --- updated-dependencies: - dependency-name: tar dependency-version: dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/browser_library_test/npm_and_yarn-eff1590ef8
branch
from
10f3276 to
71740ff
Compare
|
great, now the error makes sense. I still don't know what it is 😅, but now I won't be chasing something unexpected |
|
okay, the generated HTML file for jspm changed the paths like this: - "cli-pkg-test":"./packages/cli_pkg_test/build/./cli-pkg-test/cli-pkg-test.browser.js"
+ "cli-pkg-test":"./packages/cli_pkg_test/build/../../build/npm/cli-pkg-test.browser.js" |
|
meh, I had hoped github would show a better diff basically it went from this is generated with |
|
if my understanding is correct, it seems like now the generated path uses the "real path" rather than the provided path. i.e. it replaces the symlink with the real path.. |
|
Hm, I don't see a way to make it "preserveSymlinks"... but I suppose that we can simply |
The `@jspm/generator` package seems like it now resolves symlinks by default and there is no way to turn it off unless we use file URLs (which I couldn't get to work with `file:./lib/build`). However, manually replacing the generated concrete path back to the symlinked path seems to do the trick.
1 participant
Bumps the npm_and_yarn group with 1 update in the /browser_library_test directory: tar.
Removes
tarYou can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.