This repository has been archived by the owner on Jun 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 436
Directory structure handled incorrectly in new project. #1890
Comments
seanmorris
changed the title
Directory structure incorrect in new project.
Directory structure handled incorrectly in new project.
Dec 16, 2022
Working Lockfile: https://pastebin.com/UuipAhAK |
It seems to be a bug with the new way strings are handled in anymatch 3.1.3. On line 50 of index.js, https://github.com/micromatch/anymatch/blob/master/index.js#L50 Adding the following values to the root level Note that {
"overrides": {
"brunch": {"anymatch": "3.1.2"},
".": {"anymatch": "3.1.2"}
}
} |
I've found the issue, submitted a patch, and alerted the maintainers of the dependency to watch their semver. |
It's worth noting here that a workaround was committed in a20d6a2 and released in 4.0.2 (Jan 10). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
The assets directory is not being handled correctly in a new project.
Expected behavior
The index.html file should be built to the public/ directory.
Actual behavior
The index.html file is built to the public/assets/ directory.
Environment
package.json
contentsbrunch config contents
none
The text was updated successfully, but these errors were encountered: