hyperbrew / bolt-uxp Goto Github PK

• Add error handling to execSync() to throw an error like execSync would in Node.js.

• Add standard asynchronous exec() function to Hybrid Plugin example, returning an error in the callback function.

https://forums.creativeclouddeveloper.com/t/system-call-access-for-uxp/799/30
https://forums.creativeclouddeveloper.com/t/task-scheduling-in-uxp-hybrid-plugins/6245

In the spirit of supporting various frameworks it would be nice when yarn is opt-in. To support npm we have to check if the yarn command is available and propose to use npm otherwise. There are hints that yarn can be used alongside npm. Is this correct? I'm not able to implement this right now, but happy to do so when I can.

The affected lines in create-bolt-uxp:

See full bug issue here:

https://forums.creativeclouddeveloper.com/t/additional-uxp-panel-not-loading-in-react-properly/7972

And proposed workaround:

https://forums.creativeclouddeveloper.com/t/ruxp-react-components-for-declarative-uxp-entry-points/7527/4

Currently sourcemaps aren't being picked up by UDT, find out if there's a way to get this working.

The install path is not correctly resolved. It only supports relative paths.

◇  Where do you want to create your project?
~/Desktop/Hey
◇  Info
Creating Bolt UXP in /Users/User/Current Directory/~/Desktop/Hey

From doing superficial research it seems src/hybrid is not defined in the excludes array.

As title states if your directory has spaces for ex: user/Documents/My Projects/Bolt_Project, the npx script will try to cd without properly escaping the spaces with a \ and error out.

Hi there,

just wondering if there's a library for InDesign types like photoshop?

I see in the documentation for UXP InDesign that there is a library indesign looking at the sample images but I guess this could be a private library since there is nothing on npm

https://developer.adobe.com/indesign/uxp/resources/fundamentals/dom-versioning/

Make a CLI starter like we have for Bolt CEP.

Options include:

• Where to create project

• Framework (Svelte, React, Vue)

I added ( // BOLT-UXP_SVELTE-ONLY, // BOLT-UXP_VUE-ONLY, and // BOLT-UXP_REACT-ONLY comments around.)

Also note the index.html will need to be updated with the right framework entrypoint

and the non-used framework specific files will need to be excluded

I have framework-specific package.json files like before (e.g. package.react.json etc)

• Display name

• Host App (PS, ID, AI, premierepro)

• ID (modify uxp.config.ts )

• Enable Hybrid

• If enabled, then include the src/hybrid public-hybrid directories, otherwise exclude them

• Also if enabled, then keep the enableAddon and addon object in the uxp.config.ts

• Install Dependencies

Publishing modules to npm automatically excludes .gitignore files. The . needs to be removed and the file needs to be renamed to .gitignore when copied to the template.

The following line deletes an existing folder. This could potentially erase important files without prompting the user.
https://github.com/hyperbrew/bolt-uxp/blob/master/create-bolt-uxp/src/build.ts#L148

Just wanted to bring this to attention, as the @swc-react looks promising and would be nice to use in a bolt-uxp react project, but using any of the @swc-react packages results in an error:
Uncaught ReferenceError: exports is not defined

Reading up on the main README.md file on this github repo, it is stated that "Recently the Adobe UXP team is moving away from the built-in Spectrum UXP to Spectrum Web Components."

Looking more into using Spectrum Web Components, you would normally add the package, such as "@spectrum-web-components/action-button" to use an action button.

Without defining a definition in the globals.d.ts, typescript will of course complain. But having a premade typed definition for specific components is really nice to have.

It looks like Adobe has created nice wrappers for each of these spectrum components (has supposably has support for Next.js). The documentation page can be found over here -> https://opensource.adobe.com/spectrum-web-components/using-swc-react/

However stated at the beginning, anytime any of the @swc-react packages are imported, it results in the exports is not defined error.

I could be missing a crucial step that I may have missed, but I haven't found anything clear to resolve this issue.