• Written in Typescript
• Zero dependencies
• Drupal 8+
• Drupal 7 - (Planned)
• Collaboration, feedback, and feature requests welcome

• Context Provider stores Oauth across app
• Abstract away all token management
• Hooks such as useAPI, useLazyAPI, and useLazyLogin access REST / JSON:API / Views REST etc. with user credentials in the header
• GET, POST, PATCH, and DELETE supported
• _format=json added by default. _format=hal_json can be added manually

Lazy?

Taking inspiration from Apollo GraphQL's useLazyQuery, the hooks provided can be triggered at any time, instead of when the React component is rendered.

import { DrupalProvider } from 'react-drupal-hooks'; const config = { url: 'https://d9-testing.niallmurphy.dev/', }; ReactDOM.render( <React.StrictMode> <DrupalProvider config={config}> <App /> </DrupalProvider> </React.StrictMode>, document.getElementById('root') );

import { useLazyLogin } from 'react-drupal-hooks'; ... const [login, { loading, error, data }] = useLazyLogin(); ... onClick={() => login({	username,	password,	client_id,	client_secret,	grant_type,	scope, }) }

import { isAuthenticated } from 'react-drupal-hooks'; ... {isAuthenticated() ? 'You are authenticated': 'You are not authenticated'}

Get, post, patch, or delete any data you need. eg. Views.

import { useLazyAPI } from 'react-drupal-hooks'; ... const [lazyAPI, { loading, error, data }] = useLazyAPI(); ... onClick={() => lazyAPI({ endpoint: 'node/3', method: 'PATCH', body: { nid: [{ value: '3' }], type: [{ target_id: 'article' }], title: [{ value: 'This is hardcoded to show how body works.' }], }, }) }

import { useLazyLogout } from 'react-drupal-hooks'; ... const [logout] = useLazyLogout(); ... <button onClick={() => logout()}>Logout</button>

I hope the Drupal community can share ideas on how to make this better.

There is a problem with Jest tests. They require react and react-dom as devDependencies, but this breaks production. And help writing more comprehensive tests would be welcome. Unit testing the lazy functions is difficult so I think E2E testing with Cyrpus would work better. I've seen some people talk testing Apollo's lazy queries being difficult.

License: MIT