Skip to content

Conversation

@giastfader
Copy link
Contributor

What does this PR do?
Adds some more rules to ignore specific maven+eclipse generated files (.project and .classpath files)

Motivation
Very annoying when using Eclipse

@lvca lvca merged commit 8c34277 into ArcadeData:main Sep 7, 2021
@lvca
Copy link
Contributor

lvca commented Sep 7, 2021

Thanks

mergify bot added a commit that referenced this pull request Aug 28, 2025
… 0.3.25 to 0.3.30 in /studio [skip ci]

Bumps [@jridgewell/trace-mapping](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/trace-mapping) from 0.3.25 to 0.3.30.
Changelog

*Sourced from [`@​jridgewell/trace-mapping`'s changelog](https://github.com/jridgewell/sourcemaps/blob/main/packages/trace-mapping/CHANGELOG.md).*

> [0.3.30] - 2025-08-12
> =====================
>
> * Use `default` subpath export: <jridgewell/sourcemaps@aab8d72>
> * Transform `export default` into `module.exports =` in UMD plugin: <jridgewell/sourcemaps@cf85c75>
>
> **Full Changelog**: <jridgewell/sourcemaps@trace-mapping/0.3.29...trace-mapping/0.3.30>
>
> [0.3.29] - 2025-07-01
> =====================
>
> * Optimize UMD wrapper: <jridgewell/sourcemaps@557ca37>
> * Reorder subpath exports to improve import usage: [#35](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/trace-mapping/issues/35)
>
> **Full Changelog**: <jridgewell/sourcemaps@trace-mapping/0.3.28...trace-mapping/0.3.29>
>
> [0.3.28] - 2025-06-30
> =====================
>
> * Update UMD Wrapper to fix webpack build issue: [#33](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/trace-mapping/issues/33)
> * Add `getOwnPropertyDescriptors` polyfill to support Node v6: [#34](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/trace-mapping/issues/34)
>
> **Full Changelog**: <jridgewell/sourcemaps@trace-mapping/0.3.27...trace-mapping/0.3.28>
>
> [0.3.27] - 2025-06-30
> =====================
>
> * Remove `require(esm)` support to fix bug with Node v22: <jridgewell/sourcemaps@e957842>
>
> **Full Changelog**: <jridgewell/sourcemaps@trace-mapping/0.3.26...trace-mapping/0.3.27>
>
> [0.3.26] - 2025-06-29
> =====================
>
> * Fix package types for CJS and ESM imports: <jridgewell/sourcemaps@a924ed3>
> * Add `module-sync` exports type for [require(esm)](https://joyeecheung.github.io/blog/2024/03/18/require-esm-in-node-js/): <jridgewell/sourcemaps@3836f6c>
> * Add type declaration source maps to assist go-to-definition: <jridgewell/sourcemaps@9a02665>
> * Fix map file resolution to match spec: [#36](https://github.com/jridgewell/sourcemaps/tree/HEAD/packages/trace-mapping/issues/36)
> * Accept readonly types: <jridgewell/sourcemaps@cdf32c7>
> * Rename AnyMap: <jridgewell/sourcemaps@5676069>
> * Add error messages for common issues: <jridgewell/sourcemaps@13c8987>
>
> **Full Changelog**: <jridgewell/sourcemaps@trace-mapping/0.3.25...trace-mapping/0.3.26>


Commits

* [`095a582`](jridgewell/sourcemaps@095a582) trace-mapping/0.3.30
* [`aab8d72`](jridgewell/sourcemaps@aab8d72) Use default subpath condition for fallback
* [`3c6286e`](jridgewell/sourcemaps@3c6286e) trace-mapping/0.3.29
* [`a1c0fa0`](jridgewell/sourcemaps@a1c0fa0) Reorder subpath exports
* [`d2578bd`](jridgewell/sourcemaps@d2578bd) trace-mapping/0.3.28
* [`58ea44b`](jridgewell/sourcemaps@58ea44b) Update changelogs
* [`e0c7250`](jridgewell/sourcemaps@e0c7250) Why isn't GH autolinking commit SHAs?
* [`dad4780`](jridgewell/sourcemaps@dad4780) trace-mapping/0.3.27
* [`a451cf5`](jridgewell/sourcemaps@a451cf5) Update changelogs
* [`e957842`](jridgewell/sourcemaps@e957842) Remove `require(esm)` support from package.json
* Additional commits viewable in [compare view](https://github.com/jridgewell/sourcemaps/commits/trace-mapping/0.3.30/packages/trace-mapping)
  
[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility\_score?dependency-name=@jridgewell/trace-mapping&package-manager=npm\_and\_yarn&previous-version=0.3.25&new-version=0.3.30)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
Dependabot commands and options
  
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show  ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants