chore(ci/docs/playground): clean dependencies, add linting, update readme#31
chore(ci/docs/playground): clean dependencies, add linting, update readme#31kheiner wants to merge 24 commits intorolleyio:nextfrom
Conversation
The previous example used a collection that is not available in the playground and suggested that directus_webhooks could be read with readItems(). updated for clarity.
|
@kheiner is attempting to deploy a commit to the Rolley Team on Vercel. A member of the Team first needs to authorize it. |
Removed package-lock.json to avoid conflicts with bun.lock. Added playground/tsconfig.json to eliminate ambiguity for lsp
This should help ensure that all playground cases use a consistent directus instance.
The previous example used a collection that is not available in the playground and suggested that directus_webhooks could be read with readItems(). updated for clarity.
kheiner
left a comment
kheiner
left a comment
There was a problem hiding this comment.
The linting caught a lot of errors, glad it will be implemented forward.
I think the pipeline doesn't capture updating the docs hosted on your domain; they appear to not match the main or next branch currently.
Chore/remove npm artifacts
Docs/add linting
|
opted to merge #32 here. I'm not quite sure how you'll want me to tag the versions with your new pipeline setup. In the new setup at least I can identify that there should be fewer micro PR's. Moving comment from other PR here:
|
The strict-peer-dependencies is not supported by BUN. https://bun.com/docs/pm/npmrc#npmrc-support
fixes warning for non-explicit build command [using nuxt/starter/module as example](https://github.com/nuxt/starter/blob/6b698a45323ce40e05349c6ccd8a08fe8f791155/package.json#L28-L38)
kheiner
changed the title
change-case is not a dependency found in the module. Last seen in a deleted oas/index.ts file https://github.com/rolleyio/nuxt-directus-sdk/blob/9a3c65286d66ecf454b6402582671cca6d4b6c78/src/runtime/oas/index.ts#L1
The latest tag in devtools pulled in a development branch.
defu: No conflicts found. Researched object merging for `import as *` bug. All other minor version bumps were not fixes or changes relevant to consumers of code. ufo: No conflicts found. Three functions had fixes `hasProtocol`, `withBase`, and `withoutBase`. None are used in project.
Verified no conflicts with bumping from 4.0.0 to 4.4.2:
=> docs: Updated to use non-deprecated `throw createError({` in examples
NOTE: Removed commented line from eslint.config.js to see if that fixes the CI error.
Note: I'm not sure how these weren't caught/fixed by linter before. May require some investigation.
1.6.3 and 1.6.4 are the same release code, only change is the notice of incompatability with rolldown-vite. (doesn't apply) vuejs/vitepress@v1.6.3...v1.6.4
Reviewed documentation for breaking changes, none apply to tests as written. Verified clean install & all tests pass.
Add ignore statements to intentional `markdown/heading-increment` in docs. Apply recommendations for e18e/prefer-regex-test. Manually tested this for both instances and it still works.
This reverts commit 84deaa4.
Supports node 24. Checkout v4 supported node 20.20.2 => eslint 10.2 showed rqeuiring version node 20.19.
This reverts commit c42c0c7.
This reverts commit d0dcb9f.
|
Outstanding to do's as of right now:
In both of those packages I made contributions to support the Feedback Requested: This exercise of bumping packages makes me want to invest time into building tests for everything: so much easier to bump and test once you know you have a good set of tests up. |
|
I think it's probably better to bump it. I probably should have bumped it before we went with version 5. The user can just use version 4 of the Nuxt Directus SDK if they need to support an older version of Directus. So yeah, I think we just say that version 5 requires the latest version of Directus and that the user can use v4 of the nuxt-directus-sdk if backwards compatibility is needed? |
2 participants
This PR replaces #27.
directus-template-clipackage.jsonscripts for explicit-build warning@nuxt/kitlatest is 4.4.2Notes:
docs/guide/server-side.mdto Web API Naming conventions forthrow createError({...(statusCode=>status&&message=>statusText)change-caseis no longer used natively in the moduledefu: bump from 6.1.1...6.1.7import * asis usedhttp-proxy: verified still in use & on latest packageufo: bump from 1.6.1...1.6.3hasProtocolis not usedwithBaseis not usedwithoutBaseis not usedInspect Breaking Changes
Details by Dependency
eslint 10.20.0and@antfu/eslint-config 8.2.0#33 ]REVIEWING| NOT-BUMPING ]REVIEWING| NOT-BUMPING ]REVIEWINGv2.0.0 ]BUMPING]latestcaused issues with the nuxt team preparing for v5. In shortlatestcaptured unstable versions of dev tools.BUMPINGv4.0.2 ]^4.0.2eslint 10.20.0and@antfu/eslint-config 8.2.0#33 ]BUMPINGv4.1.4 ]:
bun outdated