-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
isbot v4 breaking change in templates and hidden files #8407
Comments
It seems |
This is resolved by #8385 and will be available in the next release. To workaround the issue in the meantime, you can downgrade |
This is now being handled by #8415 - but will still be available in the next release |
I have released isbot@3.8.0 ( With v3.8.0 users will be able to import the "isbot" property using the same syntax as a named import import { isbot } from "isbot" // works on >=3.8.0, >=4.0.0 Hope this will make the migration easier |
For me, the added line is And running
I fixed this by changing the version requirement to be specific: |
Resolved via #8415 |
🤖 Hello there, We just published version Thanks! |
1 similar comment
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
1 similar comment
🤖 Hello there, We just published version Thanks! |
Reproduction
npx create-remix@latest
with all default optionsentry.server.ts
npm remove isbot
npm install
to make sure the dependency is removed fromnode_modules
npm run dev
It will print the following and add
"isbot": "latest"
topackage.json
:Note: As of this issue being filed, it appears a new version has been marked as
latest
, so the breaking v4 version is no longer installed. As such, the reproduction doesn't break anything. However, the breaking v4 version will be marked aslatest
soon.If you want to break it now, run
npm install isbot@next
to install the newisbot@4
.https://www.npmjs.com/package/isbot#version-4-will-become-the-latest-version-on-npm-on-january-2024
System Info
Used Package Manager
npm
Expected Behavior
The dev server should build and start up without issue.
Actual Behavior
The app fails to build with an invalid import error.
The text was updated successfully, but these errors were encountered: