Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
@bustle/graphql-loader
Advanced tools
Readme
A webpack loader for .graphql
file query documents. Supports imports, outputting as strings or document ASTs, schema validation, and query hashing.
This was originally forked from https://github.com/samsarahq/graphql-loader & then heavily modified. Thank you to the authors.
npm install --save-dev @bustle/graphql-loader
Add the loader to your webpack config:
module.exports = {
// ...
module: {
rules: [
{
test: /\.graphql$/,
use: [
{
loader: '@bustle/graphql-loader',
options: {
// See "Loader Options" below
}
}
]
}
]
}
}
The path to your graphql introspection query schema JSON file. If used with the validate
option, this will be used to validate imported queries and fragments.
If true
, the loader will validate the imported document against your specified schema
file.
Specifies whether or not the imported document should be a printed graphql string, or a graphql DocumentNode
AST.
If true
and the output
option is string
, the loader will strip comments and whitespace from the graphql document strings. This helps to reduce bundled code size.
If true
, the loader will remove unused fragments from the imported document. This may be useful if a query is importing fragments from a file, but does not use all fragments in that file.
If true
, exports an additional constant named hash
which is a sha256 hash of the query contents. This can be used for persisted queries.
If 'replace'
is specified, the default export will be replaced with the hash instead of exporting the query. Useful in a production environment if your server is aware of the persisted hashes and you don't want to bundle the queries.
If using the hash
option, you can supply a custom hashing function. If not specified, uses node crypto.
If you use the hash
options of the loader for persisted queries, you can optionally add the companion plugin which will output a json manifest of all the queries with their corresponding hash. You could then use this manifest to prime your server with the persisted queries.
const { GraphQLLoaderPlugin } = require('@bustle/graphql-loader')
module.exports = {
// ...
plugins: [
new GraphQLLoaderPlugin({
manifestFilename: 'graphql-hash-manifest.json' // Optional filename option. This is the default
})
]
}
.graphql
filesThe loader supports importing .graphql
files from other .graphql
files using an #import
statement. For example:
query.graphql
:
#import "./fragments.graphql"
query {
...a
...b
}
fragments.graphql
:
fragment a on A {}
fragment b on A {
foo(bar: 1)
}
In the above example, fragments a
and b
will be made available within query.graphql
. Note that all fragments in the imported file should be used in the top-level query, or the removeUnusedFragments
should be specified.
FAQs
GraphQL Loader for Webpack
The npm package @bustle/graphql-loader receives a total of 349 weekly downloads. As such, @bustle/graphql-loader popularity was classified as not popular.
We found that @bustle/graphql-loader demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 22 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.