You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`webpack-dev-server` compiles and makes your app available @ `https//localhost:PORT`. It incrementally compiles your app as you make changes & [react-hot-loader](https://github.com/gaearon/react-hot-loader) allows modules to be hot reloaded without refreshing the page.
107
-
108
-
Updates will only show for you and not impact any other users in that environment (until you deploy).
106
+
`vite` compiles and makes your app available @ `https//localhost:PORT`. It incrementally compiles your app as you make changes allows modules to be hot reloaded without refreshing the page.
109
107
110
108
You can see how this is configured by looking at [`force-app/main/default/pages/App.page`](https://github.com/ChuckJonas/bad-ass-salesforce-stack/blob/e7b7366ca2ad1e13bc9b3a1986ad6148097c2fa2/force-app/main/default/pages/App.page#L17). Basically, we just have two output panels that render conditionally based on the url param `local == 1`.
111
109
@@ -138,10 +136,6 @@ _Note: You can have multiple VF pages_
138
136
139
137
**NOTE: If you include other static resources in the `force-app/main/default/staticresources` folder they will get nuked by default. To prevent this, update the `copy-bundle` script **
140
138
141
-
### antd theme
142
-
143
-
You can change the antd theme less variables by editing `/styles/ant-theme-vars.less`. Unfortunately, changes here require a webpack restart to show up :(
144
-
145
139
### ts-force configuration
146
140
147
141
This project comes equipped with `ts-force` to allow you typed access to Salesforce Rest API. To use `ts-force`, you must first generate classes for the SObjects you want to work with.
@@ -173,7 +167,7 @@ It is possible to debug right from vscode. To do so:
173
167
174
168
Overtime, this project has gotten both simpler AND objectively better.
175
169
176
-
Unfortunately upgrades are currently a very manual process. Over the many different enhancements:
170
+
Unfortunately upgrades are currently a very manual process. Overtime:
177
171
178
172
- configuration files have been changed & moved around
179
173
- Low Value / High Complexity: features have been removed
@@ -183,35 +177,16 @@ Unfortunately upgrades are currently a very manual process. Over the many differ
183
177
184
178
I admit, I haven't done a very good job of documenting these changes very well. My goal of keeping this everything as flexible as possible has also made it impossible to move parts of the configuration to upgradable packages.
185
179
186
-
I've tried to go back and tag `Release` to give a sense of breaking changes, but it's very incomplete.
187
-
188
-
### Things to consider when upgrading
189
-
190
-
- Most changes have happened in the following areas:
191
-
-`package.json` (particularly the `scripts` & `config` sections)
192
-
-`webpack.config.ts`
193
-
-`tsconfig.json`
194
-
195
-
For these files, it's best to first identify any customization of your own and then try to merge them into the latest version from `B.A.S.S.`.
196
-
197
-
- Lots of files have been moved around. In particular:
198
-
199
-
- many files have been moved to `config` folder.
200
-
-`src` has been renamed to `app`
201
-
202
-
- Features & dependencies have been removed. Examples:
180
+
### Upgrading to 2.0.0
203
181
204
-
- there is no longer an `local` mode as it no longer has any advantages over using `Localhost assets on salesforce`
205
-
- Redux was removed from the core of this project
206
-
- Replaced `awesome-typescript-loader` with babel
207
-
- self-signed cert generation script has been removed (manual instructions are in `config/cert`)
182
+
Version 2.0.0 is a major upgrade to the project. It includes the following changes:
208
183
209
-
-Runtime dependencies have been upgraded to the latest and greatest. Which likely means breaking changes in these libraries:
210
-
- react
211
-
- antd
212
-
- ts-force
184
+
-Upgrade to React18
185
+
- Replace Webpack with Vite
186
+
- Replacing Jest/Enzyme with Vitest/React Testing Library
187
+
- Upgrade to antd v5 (changes to theming, removes LESS support by default)
213
188
214
-
In most cases you should just be able to continue using your runtime library versions with the latest version of `B.A.S.S.`.
189
+
The easiest way to upgrade is to start a new project and copy over your files.
215
190
216
191
## OTHER USEFUL STUFF
217
192
@@ -221,18 +196,18 @@ Highly recommend using vscode (typescript code completion, in editor terminal, e
221
196
222
197
plugins:
223
198
224
-
\*
225
199
226
200
-[Editor Config](https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig): auto-set formatting options for everyone
227
201
-[TSlint](https://marketplace.visualstudio.com/items?itemName=eg2.tslint): green squigglies everywhere!
228
202
-[Salesforce Extensions for VS Code](https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode): gives your code completion on your `force-app` and ability to excute commands against the CLI
229
-
-[Jest](https://marketplace.visualstudio.com/items?itemName=Orta.vscode-jest): run tests on save
203
+
-[ViTest](https://marketplace.visualstudio.com/items?itemName=ZixuanChen.vitest-explorer): run tests in vscode
230
204
231
205
### helpful linkies
232
206
233
207
-[typescript deep dive](https://basarat.gitbooks.io/typescript/content/)
-[Where to Hold React Component Data: state, store, static, and this](https://medium.freecodecamp.org/where-do-i-belong-a-guide-to-saving-react-component-data-in-state-store-static-and-this-c49b335e2a00)
238
213
-[Redux: How to chain async actions](https://github.com/reactjs/redux/issues/1676)
0 commit comments