-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump bob-the-bundler
to latest version
#2481
base: master
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 001019f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
import { InternalAppContext } from './application'; | ||
import { ExecutionContextBuilder } from './context'; | ||
import { Application } from './types'; | ||
import { uniqueId } from '../shared/utils.js'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all those extension changes was done via bob bootstrap
}, | ||
"buildOptions": { | ||
"copy": [ | ||
"LICENSE.md", | ||
"README.md" | ||
] | ||
} | ||
}, | ||
"type": "module" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the main reason I've considered a major bump.
It might impact in some projects
Description
This PR updates
bob-the-bundler
to the latest version, including a few fixes for modern TS settings.Fixes #2480
The only changes I've made were:
bob bootstrap
so it can fix the package.json and the importsI've considered it a breaking change because how it declares the package.json changed a lot.
Type of change
Please delete options that are not relevant.
Screenshots/Sandbox (if appropriate/relevant):
How Has This Been Tested?
To test if that would work as expected, I've published it to a local npm registry, installed the new versions, and everything seems to be working fine.
Test Environment:
graphql-modules
:Checklist:
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...