# Hoisting

In resource publishing, preserving an unresolved value for substitution at a later deployment or runtime stage.

Also known as: value hoisting

In Aspire publishing discussions, hoisting describes leaving a value unresolved so a later stage can provide it. It is not JavaScript's declaration-hoisting behavior.

Structured endpoint and parameter references preserve the information a publisher needs to emit an appropriate placeholder or deployment expression. The exact representation and resolution stage depend on the deployment target.

## Practical example

Keep a resource endpoint as a deployment-time reference instead of embedding the localhost address allocated during development.

## Learn more

- [Understand structured values in resource hierarchies](https://aspire.dev/architecture/resource-hierarchies/)

## Related terms

- [Deferred evaluation](https://aspire.dev/hub/glossary/deferred-evaluation/)

- [Publisher](https://aspire.dev/hub/glossary/publisher/)

- [ReferenceExpression](https://aspire.dev/hub/glossary/referenceexpression/)